Mobility enhancement with network slicing

ABSTRACT

Wireless communications systems and methods related to mobility with consideration for network slicing are provided. In one embodiment, a user equipment (UE) transmits in a first cell frequency of a network, a request for a network slice of the network that is not provided by the first cell frequency. The UE receives, in response to the request, an information for communicating in a second cell frequency of the network that provides the requested network slice. In one embodiment, a core network entity receives, from a network entity operating over a first cell frequency of a network, a request to provide a network slice of the network to a UE, the network slice not provided by the first cell frequency. The core network entity transmits, to the BS, information associated with a second cell frequency of the network providing the network slice.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a divisional application of U.S. patentapplication Ser. No. 16/936,307, filed Jul. 22, 2020, which claimspriority to and the benefit of U.S. Provisional Patent Application No.62/880,531, filed Jul. 30, 2019, each of which is hereby incorporated byreference in its entirety as if fully set forth below and for allapplicable purposes.

INTRODUCTION

Wireless communications systems are widely deployed to provide varioustypes of communication content such as voice, video, packet data,messaging, broadcast, and so on. These systems may be capable ofsupporting communication with multiple users by sharing the availablesystem resources (e.g., time, frequency, and power). A wirelessmultiple-access communications system may include a number of basestations (BSs), each simultaneously supporting communications formultiple communication devices, which may be otherwise known as userequipment (UE).

To meet the growing demands for expanded mobile broadband connectivity,wireless communication technologies are advancing from the long termevolution (LTE) technology to a next generation new radio (NR)technology, which may be referred to as 5^(th) Generation (5G). Forexample, NR is designed to provide a lower latency, a higher bandwidthor a higher throughput, and a higher reliability than LTE. NR isdesigned to operate over a wide array of spectrum bands, for example,from low-frequency bands below about 1 gigahertz (GHz) and mid-frequencybands from about 1 GHz to about 6 GHz, to high-frequency bands such asmillimeter wave (mmWave) bands. NR is also designed to operate acrossdifferent spectrum types, from licensed spectrum to unlicensed andshared spectrum. Spectrum sharing enables operators to opportunisticallyaggregate spectrums to dynamically support high-bandwidth services.Spectrum sharing can extend the benefit of NR technologies to operatingentities that may not have access to a licensed spectrum.

The improved latency, reliability, bandwidth, and/or throughput in NRenable various types of network deployments and/or services such asenhanced mobile broadband (eMBB), ultra-reliable, low-latencycommunication (URLLC), and/or Internet of Things (IoT) services. Thedifferent types of services may have different traffic requirements(e.g., latency, bandwidth, reliability, and/or throughput).

BRIEF SUMMARY OF SOME EXAMPLES

The following summarizes some aspects of the present disclosure toprovide a basic understanding of the discussed technology. This summaryis not an extensive overview of all contemplated features of thedisclosure and is intended neither to identify key or critical elementsof all aspects of the disclosure nor to delineate the scope of any orall aspects of the disclosure. Its sole purpose is to present someconcepts of one or more aspects of the disclosure in summary form as aprelude to the more detailed description that is presented later.

For example, in an aspect of the disclosure, a method of wirelesscommunication, comprising transmitting, by a user equipment (UE) in afirst cell frequency of a network, a request for a network slice of thenetwork that is not provided by the first cell frequency; and receiving,by the UE in response to the request, information for communicating in asecond cell frequency of the network that provides the network slicerequested.

In an additional aspect of the disclosure, a method of wirelesscommunication, comprising obtaining, by a base station (BS), anindication that a user equipment (UE) is interested in a network sliceof a network not provided by a first cell frequency, the BS incommunication with the UE in the first cell frequency; and receiving, bythe BS from a core network entity, information associated with a secondcell frequency of the network providing the network slice.

In an additional aspect of the disclosure, a user equipment (UE)comprising a transceiver configured to transmit, in a first cellfrequency of a network, a request for a network slice of the networkthat is not provided by the first cell frequency; and receive, inresponse to the request, an information for communicating in a secondcell frequency of the network that provides the network slice requested.

In an additional aspect of the disclosure, a base station (BS)comprising a processor configured to obtain an indication that a userequipment (UE) is interested in a network slice of a network notprovided by a first cell frequency, the BS in communication with the UEin the first cell frequency; and a transceiver configured to receiving,by the BS from a core network entity, information associated with asecond cell frequency of the network providing the network slice.

Other aspects, features, and embodiments of the present invention willbecome apparent to those of ordinary skill in the art, upon reviewingthe following description of specific, exemplary embodiments of thepresent invention in conjunction with the accompanying figures. Whilefeatures of the present invention may be discussed relative to certainembodiments and figures below, all embodiments of the present inventioncan include one or more of the advantageous features discussed herein.In other words, while one or more embodiments may be discussed as havingcertain advantageous features, one or more of such features may also beused in accordance with the various embodiments of the inventiondiscussed herein. In similar fashion, while exemplary embodiments may bediscussed below as device, system, or method embodiments it should beunderstood that such exemplary embodiments can be implemented in variousdevices, systems, and methods.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates a wireless communication network according to someembodiments of the present disclosure.

FIG. 2 illustrates a wireless communication network system thatimplements network slicing according to some embodiments of the presentdisclosure.

FIG. 3 is a signaling diagram illustrating a network registration methodaccording to some embodiments of the present disclosure.

FIG. 4 is a block diagram of a user equipment (UE) according to someembodiments of the present disclosure.

FIG. 5 is a block diagram of an exemplary base station (BS) according tosome embodiments of the present disclosure.

FIG. 6 is a block diagram of an exemplary network unit according to someembodiments of the present disclosure.

FIG. 7 is a signaling diagram illustrating a network slicingprovisioning method according to some embodiments of the presentdisclosure.

FIG. 8 is a signaling diagram illustrating a network slicingprovisioning method according to some embodiments of the presentdisclosure.

FIG. 9A is a signaling diagram illustrating a network slicingprovisioning method according to some embodiments of the presentdisclosure.

FIG. 9B is a signaling diagram illustrating a network slicingprovisioning method according to some embodiments of the presentdisclosure.

FIG. 10 is a signaling diagram illustrating a network slicingprovisioning method according to some embodiments of the presentdisclosure.

FIG. 11 is a signaling diagram illustrating a network slicingprovisioning method according to some embodiments of the presentdisclosure.

FIG. 12 is a signaling diagram illustrating a network slicingprovisioning method according to some embodiments of the presentdisclosure.

FIG. 13A illustrates a network slice-aware handover scenario withnetwork slicing according to some embodiments of the present disclosure.

FIG. 13B is a signaling diagram illustrating a network slice-awarehandover method according to some embodiments of the present disclosure.

FIG. 14 is a flow diagram of a communication method according to someembodiments of the present disclosure.

FIG. 15 is a flow diagram of a communication method according to someembodiments of the present disclosure.

FIG. 16 is a flow diagram of a communication method according to someembodiments of the present disclosure.

FIG. 17 is a flow diagram of a communication method according to someembodiments of the present disclosure.

FIG. 18 illustrates an example call flow diagram of a network thatsupports mobility that considers network slicing factors, in accordancewith certain aspects of the present disclosure.

DETAILED DESCRIPTION

The detailed description set forth below, in connection with theappended drawings, is intended as a description of variousconfigurations and is not intended to represent the only configurationsin which the concepts described herein may be practiced. The detaileddescription includes specific details for the purpose of providing athorough understanding of the various concepts. However, it will beapparent to those skilled in the art that these concepts may bepracticed without these specific details. In some instances, well-knownstructures and components are shown in block diagram form in order toavoid obscuring such concepts.

This disclosure relates generally to wireless communications systems,also referred to as wireless communications networks. In variousembodiments, the techniques and apparatus may be used for wirelesscommunication networks such as code division multiple access (CDMA)networks, time division multiple access (TDMA) networks, frequencydivision multiple access (FDMA) networks, orthogonal FDMA (OFDMA)networks, single-carrier FDMA (SC-PUMA) networks, LTE networks, GlobalSystem for Mobile Communications (GSM) networks, 5th Generation (5G) ornew radio (NR) networks, as well as other communications networks. Asdescribed herein, the terms “networks” and “systems” may be usedinterchangeably.

An OFDMA network may implement a radio technology such as evolved UTRA(E-UTRA), Institute of Electrical and Electronics Engineers (IEEE)802.11, IEEE 802.16, IEEE 802.20, flash-OFDM and the like. UTRA, E-UTRA,and GSM are part of universal mobile telecommunication system (UMTS). Inparticular, long term evolution (LTE) is a release of UMTS that usesE-UTRA. UTRA, E-UTRA, GSM, UMTS and LTE are described in documentsprovided from an organization named “3rd Generation Partnership Project”(3GPP), and cdma2000 is described in documents from an organizationnamed “3rd Generation Partnership Project 2” (3GPP2). These variousradio technologies and standards are known or are being developed. Forexample, the 3rd Generation Partnership Project (3GPP) is acollaboration between groups of telecommunications associations thataims to define a globally applicable third generation (3G) mobile phonespecification. 3GPP long term evolution (LTE) is a 3GPP project whichwas aimed at improving the UMTS mobile phone standard. The 3GPP maydefine specifications for the next generation of mobile networks, mobilesystems, and mobile devices. The present disclosure is concerned withthe evolution of wireless technologies from LTE, 4G, 5G, NR, and beyondwith shared access to wireless spectrum between networks using acollection of new and different radio access technologies or radio airinterfaces.

In particular, 5G networks contemplate diverse deployments, diversespectrum, and diverse services and devices that may be implemented usingan OFDM-based unified, air interface. In order to achieve these goals,further enhancements to LTE and LTE-A are considered in addition todevelopment of the new radio technology for 5G NR networks. The 5G NRwill be capable of scaling to provide coverage (1) to a massive Internetof things (IoTs) with a ULtra-high density (e.g., ˜1M nodes/km²),ultra-low complexity (e.g., ˜10 s of bits/sec), ultra-low energy (e.g.,˜10+ years of battery life), and deep coverage with the capability toreach challenging locations; (2) including mission-critical control withstrong security to safeguard sensitive personal, financial, orclassified information, ultra-high reliability (e.g., ˜99.9999%reliability), ultra-low latency (e.g., ˜1 ms), and users with wideranges of mobility or lack thereof; and (3) with enhanced mobilebroadband including extreme high capacity (e.g., ˜10 Tbps/km²), extremedata rates (e.g., multi-Gbps rate, 100+ Mbps user experienced rates),and deep awareness with advanced discovery and optimizations.

The 5G NR may be implemented to use optimized OFDM-based waveforms withscalable numerology and transmission time interval (TTI); having acommon, flexible framework to efficiently multiplex services andfeatures with a dynamic, low-latency time division duplex(TDD)/frequency division duplex (FDD) design; and with advanced wirelesstechnologies, such as massive multiple input, multiple output (MIMO),robust millimeter wave (mmWave) transmissions, advanced channel coding,and device-centric mobility. Scalability of the numerology in 5G NR,with scaling of subcarrier spacing, may efficiently address operatingdiverse services across diverse spectrum and diverse deployments. Forexample, in various outdoor and macro coverage deployments of less than3 GHz FDD/TDD implementations, subcarrier spacing may occur with 15 kHz,for example over 5, 10, 20 MHz, and the like bandwidth (BW). For othervarious outdoor and small cell coverage deployments of TDD greater than3 GHz, subcarrier spacing may occur with 30 kHz over 80/100 MHz BW. Forother various indoor wideband implementations, using a TDD over theunlicensed portion of the 5 GHz band, the subcarrier spacing may occurwith 60 kHz over a 160 MHz BW. Finally, for various deploymentstransmitting with mmWave components at a TDD of 28 GHz, subcarrierspacing may occur with 120 kHz over a 500 MHz BW.

The scalable numerology of the 5G NR facilitates scalable TTI fordiverse latency and quality of service (QoS) requirements. For example,shorter TTI may be used for low latency and high reliability, whilelonger TTI may be used for higher spectral efficiency. The efficientmultiplexing of long and short TTIs to allow transmissions to start onsymbol boundaries. 5G NR also contemplates a self-contained integratedsubframe design with uplink/downlink scheduling information, data, andacknowledgement in the same subframe. The self-contained integratedsubframe supports communications in unlicensed or contention-basedshared spectrum, adaptive uplink/downlink that may be flexiblyconfigured on a per-cell basis to dynamically switch between uplink anddownlink to meet the current traffic needs.

Various other aspects and features of the disclosure are furtherdescribed below. It should be apparent that the teachings herein may beembodied in a wide variety of forms and that any specific structure,function, or both being disclosed herein is merely representative andnot limiting. Based on the teachings herein one of an ordinary level ofskill in the art should appreciate that an aspect disclosed herein maybe implemented independently of any other aspects and that two or moreof these aspects may be combined in various ways. For example, anapparatus may be implemented or a method may be practiced using anynumber of the aspects set forth herein. In addition, such an apparatusmay be implemented or such a method may be practiced using otherstructure, functionality, or structure and functionality in addition toor other than one or more of the aspects set forth herein. For example,a method may be implemented as part of a system, device, apparatus,and/or as instructions stored on a computer readable medium forexecution on a processor or computer. Furthermore, an aspect maycomprise at least one element of a claim.

NR may employ network slicing to configure multiple network slices tosupport traffic with different traffic requirements. A network slicegenerally refers to a logical network that comprises a set of networkfunctions and corresponding resources necessary to provide certainnetwork capabilities and network characteristics. A network slice mayinclude functions of an access network (AN) and a core network (CN). Anetwork slice instance (NSI) is an instantiation of a network slice,i.e. a deployed set of network functions delivering the intended networkslice services according to a network slice template.

In an example, a network slice comprises control plane and user planefunctionality and resources required to fulfill a particular service orset of services and may include: 1) core network control plane and userplane network functions, as well as their resources (in terms ofcompute, storage and network resources, including transport resourcesbetween the network functions); 2) a radio access network; and 3) in thecase of a network slice supporting a roaming service, a visitor publicland mobile network (VPLMN) part and a home PLMN (HPLMN) part.

In some examples, a UE may simultaneously require multiple services ofdifferent traffic requirements. For example, the UE may require anenhanced mobile broadband (eMBB) service with a high throughput and anultra-reliable, low-latency communication (URLLC) service. However, withnetwork slicing, operators may typically deploy one or more networkslice with a high throughput over a certain frequency carrier (e.g., F1)for serving eMBB services and one or more network slice with alow-latency over another frequency carrier (e.g., F2) for serving URLLCservices. In other words, if a UE is on the frequency carrier F1, the UEmay have access to eMBB slices, but no access to URLLC slices.Similarly, if a UE is on the frequency carrier F2, the UE may haveaccess to URLLC slices, but no access to eMBB slices.

The present application describes mechanisms for performing mobilitywith network slicing into consideration. For example, a UE is associatedwith a first cell frequency of a network or a BS operating over thefirst cell frequency. The association can be based on a cell selection,a camping procedure, a random access procedure, a connection set upprocedure, and/or a network registration. The UE may be interested in aparticular network slice of the network that is not allowed, available,or supported by the first cell frequency. The particular network slicemay not be within allowed network slice selection assistance information(NSSAI) of the first cell frequency. The particular network slice may beserved over a second cell frequency of the network. The UE may requestthe network for the interested network slice over the first cellfrequency via non-access stratum (NAS) signaling, radio resource control(RRC) signaling, and/or on-demand system information block (SIB)requests. The network can instruct the UE to perform a handover to thesecond cell frequency, a dual-connectivity with the second cellfrequency, or a carrier aggregation with the second cell frequency. TheUE may perform the handover, the dual-connectivity, or the carrieraggregation accordingly. Subsequently, the UE may receive a service overthe particular network slice in the second cell frequency. In anembodiment, the BS may be in communication with a core network thatmanages the network slices in the network. The core network may providethe BS with information associated with the UE's interested networkslice and/or information associated with the second cell frequency thatprovides the UE's interested slice.

Aspects of the present disclosure can provide several benefits. Forexample, the enabling of the UE to request for the particular networkslice not included in the allowed NSSAI allows the UE to dynamicallyrequest for the network slice based on service initiation and/orapplication initiation at the UE. The on-demand SIB request for networkslice information enables the UE to perform network slice-based cellselection and/or network slice-aware cell reselection. The provisioningof information associated with the UE's interested network slice to theBS enables the BS to perform network slice-based handover.

FIG. 1 illustrates a wireless communication network 100 according tosome embodiments of the present disclosure. The network 100 may be a 5Gnetwork. The network 100 includes a number of base stations (BSs) 105(individually labeled as 105 a, 105 b, 105 c, 105 d, 105 e, and 105 f)and other network entities. ABS 105 may be a station that communicateswith UEs 115 and may also be referred to as an evolved node B (eNB), anext generation eNB (gNB), an access point, and the like. Each BS 105may provide communication coverage for a particular geographic area. In3GPP, the term “cell” can refer to this particular geographic coveragearea of a BS 105 and/or a BS subsystem serving the coverage area,depending on the context in which the term is used.

A BS 105 may provide communication coverage for a macro cell or a smallcell, such as a pico cell or a femto cell, and/or other types of cell. Amacro cell generally covers a relatively large geographic area (e.g.,several kilometers in radius) and may allow unrestricted access by UEswith service subscriptions with the network provider. A small cell, suchas a pico cell, would generally cover a relatively smaller geographicarea and may allow unrestricted access by UEs with service subscriptionswith the network provider. A small cell, such as a femto cell, wouldalso generally cover a relatively small geographic area (e.g., a home)and, in addition to unrestricted access, may also provide restrictedaccess by UEs having an association with the femto cell (e.g., UEs in aclosed subscriber group (CSG), UEs for users in the home, and the like).A BS for a macro cell may be referred to as a macro BS. A BS for a smallcell may be referred to as a small cell BS, a pico BS, a femto BS or ahome BS. In the example shown in FIG. 1 , the BSs 105 d and 105 e may beregular macro BSs, while the BSs 105 a-105 c may be macro BSs enabledwith one of three dimension (3D), full dimension (PD), or massive MIMO.The BSs 105 a-105 c may take advantage of their higher dimension MIMOcapabilities to exploit 3D beamforming in both elevation and azimuthbeamforming to increase coverage and capacity. The BS 105 f may be asmall cell BS which may be a home node or portable access point. A BS105 may support one or multiple (e.g., two, three, four, and the like)cells.

The network 100 may support synchronous or asynchronous operation. Forsynchronous operation, the BSs may have similar frame timing, andtransmissions from different BSs may be approximately aligned in time.For asynchronous operation, the BSs may have different frame timing, andtransmissions from different BSs may not be aligned in time.

The UEs 115 are dispersed throughout the wireless network 100, and eachUE 115 may be stationary or mobile. A UE 115 may also be referred to asa terminal, a mobile station, a subscriber unit, a station, or the like.A UE 115 may be a cellular phone, a personal digital assistant (PDA), awireless modem, a wireless communication device, a handheld device, atablet computer, a laptop computer, a cordless phone, a wireless localloop (WLL) station, or the like. In one aspect, a UE 115 may be a devicethat includes a Universal Integrated Circuit Card (UICC). In anotheraspect, a UE may be a device that does not include a UICC. In someaspects, the UEs 115 that do not include UICCs may also be referred toas IoT devices or internet of everything (IoE) devices. The UEs 115a-115 d are examples of mobile smart phone-type devices accessingnetwork 100. A UE 115 may also be a machine specifically configured forconnected communication, including machine type communication (MTC),enhanced MTC (eMTC), narrowband IoT (NB-IoT) and the like. The UEs 115e-115 k are examples of various machines configured for communicationthat access the network 100. A UE 115 may be able to communicate withany type of the BSs, whether macro BS, small cell, or the like. In FIG.1 , a lightning bolt (e.g., communication links) indicates wirelesstransmissions between a UE 115 and a serving BS 105, which is a BSdesignated to serve the UE 115 on the downlink and/or uplink, or desiredtransmission between BSs, and backhaul transmissions between BSs.

In operation, the BSs 105 a-105 c may serve the UEs 115 a and 115 busing 3D beamforming and coordinated spatial techniques, such ascoordinated multipoint (CoMP) or multi-connectivity. The macro BS 105 dmay perform backhaul communications with the BSs 105 a-105 c, as well assmall cell, the BS 105 f. The macro BS 105 d may also transmitsmulticast services which are subscribed to and received by the UEs 115 cand 115 d. Such multicast services may include mobile television orstream video, or may include other services for providing communityinformation, such as weather emergencies or alerts, such as Amber alertsor gray alerts.

The BSs 105 may also communicate with a core network. The core networkmay provide user authentication, access authorization, tracking,Internet Protocol (IP) connectivity, and other access, routing, ormobility functions. At least some of the BSs 105 (e.g., which may be anexample of a gNB or an access node controller (ANC)) may interface withthe core network through backhaul links (e.g., NG-C, NG-U, etc.) and mayperform radio configuration and scheduling for communication with theUEs 115. In various examples, the BSs 105 may communicate, eitherdirectly or indirectly (e.g., through core network), with each otherover backhaul links (e.g., X1, X2, etc.), which may be wired or wirelesscommunication links.

The network 100 may also support mission critical communications withultra-reliable and redundant links for mission critical devices, such asthe UE 115 e, which may be a drone. Redundant communication links withthe UE 115 e may include links from the macro BSs 105 d and 105 e, aswell as links from the small cell BS 105 f. Other machine type devices,such as the UE 115 f (e.g., a thermometer), the UE 115 g (e.g., smartmeter), and UE 115 h (e.g., wearable device) may communicate through thenetwork 100 either directly with BSs, such as the small cell BS 105 f,and the macro BS 105 e, or in multi-hop configurations by communicatingwith another user device which relays its information to the network,such as the UE 115 f communicating temperature measurement informationto the smart meter, the UE 115 g, which is then reported to the networkthrough the small cell BS 105 f. The network 100 may also provideadditional network efficiency through dynamic, low-latency TDD/FDDcommunications, such as in a vehicle-to-vehicle (V2V)

In some implementations, the network 100 utilizes OFDM-based waveformsfor communications. An OFDM-based system may partition the system BWinto multiple (K) orthogonal subcarriers, which are also commonlyreferred to as subcarriers, tones, bins, or the like. Each subcarriermay be modulated with data. In some instances, the subcarrier spacingbetween adjacent subcarriers may be fixed, and the total number ofsubcarriers (K) may be dependent on the system BW. The system BW mayalso be partitioned into subbands. In other instances, the subcarrierspacing and/or the duration of TTIs may be scalable.

In an embodiment, the BSs 105 can assign or schedule transmissionresources (e.g., in the form of time-frequency resource blocks (RB)) fordownlink (DL) and uplink (UL) transmissions in the network 100. DLrefers to the transmission direction from a BS 105 to a UE 115, whereasUL refers to the transmission direction from a UE 115 to a BS 105. Thecommunication can be in the form of radio frames. A radio frame may bedivided into a plurality of subframes or slots, for example, about 10.Each slot may be further divided into mini-slots. In a FDD mode,simultaneous UL and DL transmissions may occur in different frequencybands. For example, each subframe includes a UL subframe in a ULfrequency band and a DL subframe in a DL frequency band. In a TDD mode,UL and DL transmissions occur at different time periods using the samefrequency band. For example, a subset of the subframes (e.g., DLsubframes) in a radio frame may be used for DL transmissions and anothersubset of the subframes (e.g., UL subframes) in the radio frame may beused for UL transmissions.

The DL subframes and the UL subframes can be further divided intoseveral regions. For example, each DL or UL subframe may havepre-defined regions for transmissions of reference signals, controlinformation, and data. Reference signals are predetermined signals thatfacilitate the communications between the BSs 105 and the UEs 115. Forexample, a reference signal can have a particular pilot pattern orstructure, where pilot tones may span across an operational BW orfrequency band, each positioned at a pre-defined time and a pre-definedfrequency. For example, a BS 105 may transmit cell specific referencesignals (CRSs) and/or channel state information—reference signals(CSI-RSs) to enable a UE 115 to estimate a DL channel. Similarly, a UE115 may transmit sounding reference signals (SRSs) to enable a BS 105 toestimate a UL channel Control information may include resourceassignments and protocol controls. Data may include protocol data and/oroperational data. In some embodiments, the BSs 105 and the UEs 115 maycommunicate using self-contained subframes. A self-contained subframemay include a portion for DL communication and a portion for ULcommunication. A self-contained subframe can be DL-centric orUL-centric. A DL-centric subframe may include a longer duration for DLcommunication than for UL communication. A UL-centric subframe mayinclude a longer duration for UL communication than for ULcommunication.

In an embodiment, the network 100 may be an NR network deployed over alicensed spectrum. The BSs 105 can transmit synchronization signals(e.g., including a primary synchronization signal (PSS) and a secondarysynchronization signal (SSS)) in the network 100 to facilitatesynchronization. The BSs 105 can broadcast system information associatedwith the network 100 (e.g., including a master information block (MIB),remaining system information (RMSI), and other system information (OSI))to facilitate initial network access. In some instances, the BSs 105 maybroadcast the PSS, the SSS, and/or the MIB in the form ofsynchronization signal block (SSBs) over a physical broadcast channel(PBCH) and may broadcast the RMSI and/or the OSI over a physicaldownlink shared channel (PDSCH).

In an embodiment, a UE 115 attempting to access the network 100 mayperform an initial cell search by detecting a PSS from a BS 105. The PSSmay enable synchronization of period timing and may indicate a physicallayer identity value. The UE 115 may then receive a SSS. The SSS mayenable radio frame synchronization, and may provide a cell identityvalue, which may be combined with the physical layer identity value toidentify the cell. The PSS and the SSS may be located in a centralportion of a carrier or any suitable frequencies within the carrier.

After receiving the PSS and SSS, the UE 115 may receive a MIB. The MIBmay include system information for initial network access and schedulinginformation for RMSI and/or OSI. After decoding the MIB, the UE 115 mayreceive RMSI and/or OSI. The RMSI and/or OSI may include radio resourcecontrol (RRC) information related to random access channel (RACH)procedures, paging, control resource set (CORESET) for physical downlinkcontrol channel (PDCCH) monitoring, physical uplink control channel(PUCCH), physical uplink shared channel (PUSCH), power control, and SRS.

After obtaining the MIB, the RMSI and/or the OSI, the UE 115 can performa random access procedure to establish a connection with the BS 105. Insome examples, the random access procedure may be a four-step randomaccess procedure. For example, the UE 115 may transmit a random accesspreamble and the BS 105 may respond with a random access response. Therandom access response (RAR) may include a detected random accesspreamble identifier (ID) corresponding to the random access preamble,timing advance (TA) information, a UL grant, a temporary cell-radionetwork temporary identifier (C-RNTI), and/or a backoff indicator. Uponreceiving the random access response, the UE 115 may transmit aconnection request to the BS 105 and the BS 105 may respond with aconnection response. The connection response may indicate a contentionresolution. In some examples, the random access preamble, the RAR, theconnection request, and the connection response can be referred to as amessage 1 (MSG 1), a message 2 (MSG 2), a message 3 (MSG 3), and amessage 4 (MSG 4), respectively. In some examples, the random accessprocedure may be a two-step random access procedure, where the UE 115may transmit a random access preamble and a connection request in asingle transmission and the BS 105 may respond by transmitting a randomaccess response and a connection response in a single transmission. Thecombined random access preamble and connection request in the two-steprandom access procedure may be referred to as a message A (MSG A). Thecombined random access response and connection response in the two-steprandom access procedure may be referred to as a message B (MSG B).

After establishing a connection, the UE 115 and the BS 105 can enter anormal operation stage, where operational data may be exchanged. Forexample, the BS 105 may schedule the UE 115 for UL and/or DLcommunications. The BS 105 may transmit UL and/or DL scheduling grantsto the UE 115 via a PDCCH. The BS 105 may transmit a DL communicationsignal to the UE 115 via a PDSCH according to a DL scheduling grant. TheUE 115 may transmit a UL communication signal to the BS 105 via a PUSCHand/or PUCCH according to a UL scheduling grant. The connection may bereferred to as an RRC connection. When the UE 115 is actively exchangingdata with the BS 105, the UE 115 is in an RRC connected state.

In an example, after establishing a connection with the BS 105, the UE115 may initiate an initial network attachment procedure with thenetwork 100. The BS 105 may coordinate with various network entities orfifth generation core (5GC) entities, such as an access and mobilityfunction (AMF), a serving gateway (SGW), and/or a packet data networkgateway (PGW), to complete the network attachment procedure. Forexample, the BS 105 may coordinate with the network entities in the 5GCto identify the UE, authenticate the UE, and/or authorize the UE forsending and/or receiving data in the network 100. In addition, the AMFmay assign the UE with a group of tracking areas (TAs). Once the networkattach procedure succeeds, a context is established for the UE 115 inthe AMF. After a successful attach to the network, the UE 115 can movearound the current TA. For tracking area update (TAU), the BS 105 mayrequest the UE 115 to update the network 100 with the UE 115's locationperiodically. Alternatively, the UE 115 may only report the UE 115'slocation to the network 100 when entering a new TA. The TAU allows thenetwork 100 to quickly locate the UE 115 and page the UE 115 uponreceiving an incoming data packet or call for the UE 115. A registrationarea may have one or more tracking areas. A tracking area may have oneor more cells. Additionally, a tracking area identity (TAI) is anidentifier that is used to track tracking areas. The TAI may beconstructed from the PLMN identity to which the tracking area belongsand the tracking area code (TAC) of the tracking area.

In an embodiment, the network 100 may operate over a system BW or acomponent carrier BW. The network 100 may partition the system BW intomultiple BWPs (e.g., portions). A BS 105 may dynamically assign a UE 115to operate over a certain BWP (e.g., a certain portion of the systemBW). The assigned BWP may be referred to as the active BWP. The UE 115may monitor the active BWP for signaling information from the BS 105.The BS 105 may schedule the UE 115 for UL or DL communications in theactive BWP. In some embodiments, a BS 105 may assign a pair of BWPswithin the component carrier to a UE 115 for UL and DL communications.For example, the BWP pair may include one BWP for UL communications andone BWP for DL communications.

In an embodiment, the network 100 may be a 5G network. The network 100may implement network slicing to create multiple isolated virtualnetworks or independent logical network slices to support a variety ofapplication services in the network 100. The network 100 may configureeach network slice according to the specific needs of the services beingserved. In an embodiment, the network 100 may configure a network slicewith a high throughput for serving eMBB services and configure anothernetwork slice with a low latency and high reliability for serving URLLCservices. A UE 115 may request for a particular network slice (e.g., aneMBB slice or an URLLC slice) during various network procedures and thenetwork 100 and/or the UE 115 may take network slicing in considerationduring the network procedures. Some examples of network procedures thatmay take network slicing into consideration may include cell selection,cell reselection, network registrations, network service establishments,PDU session establishments, and/or mobility. Mechanisms for provisioningfor network slicing are described in greater detail herein.

FIG. 2 illustrates a wireless communication network 200 that implementsnetwork slicing according to some embodiments of the present disclosure.The network 200 may correspond to a portion of the network 100. Thenetwork 200 may be a 5G network. The network 200 includes a radio accessnetwork (RAN) 240 in communication with a core network 230 via backhaullinks 232. For simplicity of illustration and discussions, FIG. 2illustrates three BSs 205 a, 205 b, and 205 c and three UEs 215 in theRAN 240. However, the RAN 240 may be scaled to include any suitablenumber of BSs (e.g., about 2, 4, 5, or more) and/or any suitable numberof UEs (e.g., up to millions). The BSs 205 are similar to the BSs 105.The UEs 115 are similar to the UEs 115.

In the network 200, the BS 205 a may serve UEs 215 over a frequencycarrier 220 in an area 210 a, the BS 205 b may serve UEs 215 overanother frequency carrier 222 in an area 210 b, and the BS 205 c mayserve UEs 215 over the frequency carrier 222 in an area 210 c. Thefrequency carrier 220 and the frequency carrier 222 may be at anysuitable frequency. In some examples, the frequency carrier 220 and thefrequency carrier 222 can be at sub-6 gigahertz (GHz) bands. In someexamples, the frequency carrier 220 and the frequency carrier 222 can beat mmWav bands. In some examples, one of the frequency carriers 220 and222 can be at a sub-6 GHz band and the other frequency carriers 220 and222 can be at a mmWav band.

In an example, the UEs 215 may be a smart phone requiring eMBB servicesand may additionally require URLLC services. In an example, the UE 215 amay include an extended reality (XR) application and may require anURLLC service for communicating XR application data. In an example, theUE 215 a may be a remote diagnostic device with sensors that requires anURLLC service for communicating health monitoring information. In anexample, the UE 215 a may be associated with an intelligenttransportation system that requires an URLLC service for communicatingtransport information. In some examples, the UE 215 a may require aneMBB service and URLLC services at the same time.

In an example, the core network 230 is a 5G core network and may providenetwork functions such as an authentication server function (AUSF), anAMF, a session management function (SMF), a policy control function(PCF), a user plane function (UPF), an application functions (AFs), aunified data repository (UDR), an unstructured data storage networkfunction (UDSF), a network exposure function (NEF), an NF repositoryfunction (NRF), a unified data management function (UDM), and/or anetwork slice selection function (NSSF). The BSs 205 may coordinate withthe core network 230 in serving the UEs 215.

In an example, the network 200 may implement network slicing toprovision for the eMBB services and the URLLC services. For example, thenetwork 200 may configure one or more network slices 250 over thefrequency carrier 220 and one or more network slices 252 over thefrequency carrier 222. Each of the network slices 250 and 252 mayfunction as a logical network and may implement AN and CNfunctionalities as described above. In an example, all the networkslices 250 may serve one type of services (e.g., eMBB services or URLLCservices). In an example, at least one network slice 250 may serve adifferent type of services than the other network slices 250. Similarly,in an example, all the network slices 252 may serve one type of services(e.g., eMBB services or URLLC services). In an example, at least onenetwork slice 252 may serve a different type of services than the othernetwork slices 252.

In an example, the network slices 250 over the frequency carrier F1 220may serve one or more types of services and the network slices 252 overthe frequency carrier F2 220 may serve one or more types of services,but at least one type of service is served over by one of the networkslices 250 and one of the network slices 252. For example, all networkslices 250 may serve MBB services, at least one network slice 252 mayserve URLLC services, and at least one network slice 252 may serve eMBBservices. Alternatively, at least one network slice 250 may serve MBBservices, at least one network slice 250 may serve voice services, atleast one network slice 252 may serve URLLC services, and at least onenetwork slice 252 may serve eMBB services.

In some examples, the frequency carrier 220 may be at about 2.6 GHz andmay be shared with a LTE TDD network, whereas the frequency carrier 222may be at about 4.9 GHz which may not be shared with a LTE TDD network.Due to the sharing with the LTE TDD network on the 2.6 GHz carrier,communications over the 2.6 GHz carrier may have various restrictions.For example, UL-to-DL and/or DL-to-UL switching time for communicationover the 2.6 GHz carrier is required to align to the UL-to-DL and/orDL-to-UL switching time of the LTE TDD network. Thus, some operators maydeploy eMBB slices, but not URLLC slices over the 2.6 GHz carrier.Instead, the operators may deploy URLLC slices over the less restrictive4.9 GHz carrier.

In some instances, while the UE 215 a is served by the BS 205 a over thefrequency carrier 220 for an eMBB service in a network slice 250, the UE215 a may launch an application requiring an URLLC service. Thus, thenetwork 200 is required to direct the UE 215 a to the frequency carrier222 so that the UE 215 a may receive the URLLC service in a networkslice 252. However, the selection and/or configuration of network slicesare typically performed by the core network 230 as descried in greaterdetail herein. The UE 215 a may not have knowledge about which frequencycarrier or cell in the network 200 may provide a network slice that cansupport an URLLC service. A BS 205 may be aware of the active networkslice used by a UE 215, but may not be aware of which network slice isavailable or allowed in which frequency carrier over the network 200.While the network 200 may support eMBB services and URLLC services onthe same network slice (e.g., in a network slice 252 over the frequencycarrier 222) to avoid such issues, the network 200 may not benefit fromnetwork slicing, and thus may not be desirable.

FIG. 3 is a signaling diagram illustrating a network slicingprovisioning method 300 according to some embodiments of the presentdisclosure. The method 300 may be implemented by a UE similar to the UEs115 and 215, a BS similar to the BSs 105 and 205, and an AMF (e.g., acomponent of a core network such as the core network 230). The BS andthe AMF may generally be referred to as the network side. Steps of themethod 300 can be executed by computing devices (e.g., a processor,processing circuit, and/or other suitable component) of the BS, the UE,and an AMF component. As illustrated, the method 300 includes a numberof enumerated steps, but embodiments of the method 300 may includeadditional steps before, after, and in between the enumerated steps. Insome embodiments, one or more of the enumerated steps may be omitted orperformed in a different order.

At step 310, the BS transmits a next generation (NG) setup requestmessage to the AMF. The NG setup request message indicates one or morenetwork slices (e.g., the network slices 250) supported by the BS. In anexample, the NG setup request message may include a single-network sliceselection assistance information (S-NSSAI) list per tracking area.

At step 320, in response to the NG setup request message, the AMFtransmits a NG setup response message to the BS. Based on the NG setuprequest message, the AMF may have knowledge of the network slicessupported by the BS and/or the tracking area of the BS. The AMF mayperform similar NG setup request and response message exchange withother BSs, and thus the AMF may have knowledge of network slicessupported by the other BSs and/or other tracking areas.

At step 330, the UE transmits an RRC connection setup completion messageto the BS. For example, the UE may have completed a successful randomaccess procedure with the BS. The random access procedure may includethe exchange of MSG 1, MSG 2, MSG 3, and MSG 4 described above withrespect to FIG. 1 . In some instances, the RRC connection setupcompletion message is exchanged after MSG 4, and may be referred to as amessage 5 (MSG 5).

In an example, the RRC connection setup completion message may include aNAS registration request. The NAS registration request may includerequested-NSSAI. The requested-NSSAI may indicate one or more networkslices (e.g., the network slices 250) requested by the UE, for example,based on applications that may be used by the UE or potentially used bythe UE.

At step 340, upon receiving the RRC connection setup completion messageindicating NAS registration message, the BS transmits an initial UEmessage to the AMF. The initial UE message may include the NASregistration request.

At step 350, in response to the initial UE message, the AMF transmits aninitial UE context setup request message to the BS. The initial UEcontext setup request message may include allowed NSSAI. The allowedNSSAI may indicate requested network slices that are allowed in thetracking area. The allowed NSSAI may be a minimal common set ofrequested-NSSAI, subscribed NSSAI (e.g., based on the UE'ssubscription), and NSSAI supported by a current tracking area. Theinitial UE context setup request message may include a NAS registrationaccept message including the allowed NSSAI. In an example, the UE mayinclude a slice A (e.g., the network slice 250) and a slice B (e.g., thenetwork slice 252) in the requested-NSSAI at the step 330. The AMF mayallow slice A, but may reject slice B. In such an example, the AMF mayinclude allowed NSSAI and rejected NSSAI in the initial UE context setuprequest message. The allowed NSSAI may indicate the slice A and therejected NSSAI may indicate the slice B.

At step 360, after receiving the initial UE context setup requestmessage from the AMF, the BS and the UE perform a security mode controlprocedure to exchange various security mode messages.

At step 370, after completing the security mode control procedure, theBS transmits an RRC reconfiguration message to the UE. The RRCreconfiguration message may include a NAS registration accept messageindicating allowed NSSAI. At this time, the UE may have a UE context 380including configured NSSAI (e.g., based on a pre-configuration on theUE), the requested NSSAI, the allowed NSSAI, and/or the rejected NSSAI.The BS may have a UE context 382 including the allowed NSSAI and NSSAIof active PDU sessions of the UE. The AMF may include a UE context 384including subscribed NSSAI, the requested NSSAI, the allowed NSSAI, andthe rejected NSSAI.

As can be observed from the method 300, the BS may not have knowledge ofwhat network slices are supported in the network. While the BS mayreceive rejected NSSAI in the initial UE context setup response messagefrom the AMF in the step 350, the BS may not have knowledge of whetherthe network slices indicated in the rejected NSSAI is supported over adifferent cell frequency and/or a different tracking area or not beingsupport by the network. Thus, the BS (or a RAN) may not have sufficientinformation to consider network slices that are interested or requiredby the UE when performing mobility of the UE. Similarly, when the UErequested a network slice that is not in the allowed NSSAI, the UE isnot provided with further information associated with requested networkslice. Additionally, the UE may not have knowledge of whether the UE canrequest a certain network slice (e.g., an URLLC slice) from the networkon-demand.

Further, current network slicing technology may have variousrestrictions. For example, slice support is uniform in a tracking area.Frequency carriers with different slice support are typically configuredin different tracking areas. All slices in allowed NSSAI are support bya tracking area. The UE may not be allowed to request a slice that isindicated in the rejected NSSAI except when there is a tracking areachange. The UE may only request a PDU session establishment over a slicewithin the allowed NSSAI. The restrictions on the current networkslicing technology and the lack of slice-to-frequency mappinginformation available at the BS and/or the UE may cause challenges insupporting UEs that require multiple network slices provided bydifferent frequency carriers.

Accordingly, the present disclosure provides various signalingtechniques for a UE (e.g., the UEs 115) to request a network slice thatis not supported by a cell frequency where the UE is currently camped onor by a current registered tracking area of the UE. The presentdisclosure also provides techniques for BSs (e.g., the BSs 105 and 205)and/or a RAN (e.g., the RAN 240) to take network slices that areinterested by a UE into consideration when performing mobility for theUE.

FIG. 4 is a block diagram of an exemplary UE 400 according toembodiments of the present disclosure. The UE 400 may be a UE 115 or aUE 215 discussed above in FIGS. 1 and 2 , respectively. As shown, the UE400 may include a processor 402, a memory 404, an application module407, a network slicing module 408, a transceiver 410 including a modemsubsystem 412 and a radio frequency (RF) unit 414, and one or moreantennas 416. These elements may be in direct or indirect communicationwith each other, for example via one or more buses.

The processor 402 may include a central processing unit (CPU), a digitalsignal processor (DSP), an application specific integrated circuit(ASIC), a controller, a field programmable gate array (FPGA) device,another hardware device, a firmware device, or any combination thereofconfigured to perform the operations described herein. The processor 402may also be implemented as a combination of computing devices, e.g., acombination of a DSP and a microprocessor, a plurality ofmicroprocessors, one or more microprocessors in conjunction with a DSPcore, or any other such configuration.

The memory 404 may include a cache memory (e.g., a cache memory of theprocessor 402), random access memory (RAM), magnetoresistive RAM (MRAM),read-only memory (ROM), programmable read-only memory (PROM), erasableprogrammable read only memory (EPROM), electrically erasableprogrammable read only memory (EEPROM), flash memory, solid state memorydevice, hard disk drives, other forms of volatile and non-volatilememory, or a combination of different types of memory. In an embodiment,the memory 404 includes a non-transitory computer-readable medium. Thememory 404 may store, or have recorded thereon, instructions 406. Theinstructions 406 may include instructions that, when executed by theprocessor 402, cause the processor 402 to perform the operationsdescribed herein with reference to the UEs 115 in connection withembodiments of the present disclosure, for example, aspects of FIGS.7-15 . Instructions 406 may also be referred to as program code. Theprogram code may be for causing a wireless communication device toperform these operations, for example by causing one or more processors(such as processor 402) to control or command the wireless communicationdevice to do so. The terms “instructions” and “code” should beinterpreted broadly to include any type of computer-readablestatement(s). For example, the terms “instructions” and “code” may referto one or more programs, routines, sub-routines, functions, procedures,etc. “Instructions” and “code” may include a single computer-readablestatement or many computer-readable statements.

Each of the application module 407 and the network slicing module 408may be implemented via hardware, software, or combinations thereof. Forexample, each of the application module 407 and the network slicingmodule 408 may be implemented as a processor, circuit, and/orinstructions 406 stored in the memory 404 and executed by the processor402. In some examples, the application module 407 and the networkslicing module 408 can be integrated within the modem subsystem 412. Forexample, the application module 407 and the network slicing module 408can be implemented by a combination of software components (e.g.,executed by a DSP or a general processor) and hardware components (e.g.,logic gates and circuitry) within the modem subsystem 412. In someexamples, a UE may include one or both of the application module 407 andthe network slicing module 408. In other examples, a UE may include allof the application module 407 and the network slicing module 408.

The application module 407 and the network slicing module 408 may beused for various aspects of the present disclosure, for example, aspectsof FIGS. 7-15 . The application module 407 is configured to implementtwo or more applications. The applications may have different servicerequirements (e.g., latency and/or bandwidth). The applications mayinclude at least an eMBB application (e.g., streaming and/or filetransfer) and a URLLC application (e.g., XR, remote healthcare related,or intelligent transport related). The application module 407 isconfigured to transmit a request to setup a PDU session for an eMBBservice or a URLLC service to the network slicing module 408.

The network slicing module 408 is configured to perform an associationwith a BS (e.g., the BSs 105 and/or 205) operating over a first cellfrequency (e.g., the frequency carrier 220) of a network (e.g., thenetworks 100 and/or 200) and transmit, in the first cell frequency, arequest for a particular network slice (e.g., the network slices 250 and252) of the network that is not supported in the first cell frequency.The association can be based on a cell selection, a camping procedure, arandom access procedure, a connection set up procedure, and/or a networkregistration. The request can be transmitted in a NAS registrationrequest message, a NAS service request message, a NAS PDU sessionrequest message, an RRC service indication message, or an on-demand SIBrequest message. The NAS registration request message can include one ormore requested network slices and priorities of the requested networkslices.

In an embodiment, the network slicing module 408 is configured toreceive, from the BS, an instruction to perform a handover to a secondcell frequency that supports the requested network slice, perform adual-connectivity with the second cell frequency, or perform a carrieraggregation with the second cell frequency to access the requested slicein the second cell frequency. The network slicing module 408 isconfigured to perform the handover, the dual-connectivity, or thecarrier aggregation based on the instruction received from the BS,perform a network registration requesting for the particular networkslice after the handover, the dual-connectivity, or the carrieraggregation, establish a PDU session over the network slice, and/orcommunicate data in the PDU session over the network slice.

In an embodiment, the network slicing module 408 is configured todetermine that an interested network slice is not available or allowedover a current cell frequency, transmit an on-demand SIB request torequest for frequency to network slice mapping information for theinterested network slice, receive frequency to network slice mappinginformation for the network slice, and perform a network slice-awarecell selection and/or reselection. Mechanisms for performing mobilitywith network slicing consideration are described in greater detailherein.

As shown, the transceiver 410 may include the modem subsystem 412 andthe RF unit 414. The transceiver 410 can be configured to communicatebi-directionally with other devices, such as the BSs 105. The modemsubsystem 412 may be configured to modulate and/or encode the data fromthe memory 404 and/or the network slicing module 408 according to amodulation and coding scheme (MCS), e.g., a low-density parity check(LDPC) coding scheme, a turbo coding scheme, a convolutional codingscheme, a digital beamforming scheme, etc. The RF unit 414 may beconfigured to process (e.g., perform analog to digital conversion ordigital to analog conversion, etc.) modulated/encoded data (e.g., NASmessages, RRC messages) from the modem subsystem 412 (on outboundtransmissions) or of transmissions originating from another source suchas a UE 115 or a BS 105. The RF unit 414 may be further configured toperform analog beamforming in conjunction with the digital beamforming.Although shown as integrated together in transceiver 410, the modemsubsystem 412 and the RF unit 414 may be separate devices that arecoupled together at the UE 115 to enable the UE 115 to communicate withother devices.

The RF unit 414 may provide the modulated and/or processed data, e.g.data packets (or, more generally, data messages that may contain one ormore data packets and other information), to the antennas 416 fortransmission to one or more other devices. The antennas 416 may furtherreceive data messages transmitted from other devices. The antennas 416may provide the received data messages for processing and/ordemodulation at the transceiver 410. The transceiver 410 may provide thedemodulated and decoded data (e.g., NAS messages and RRC messages) tothe network slicing module 408 for processing. The antennas 416 mayinclude multiple antennas of similar or different designs in order tosustain multiple transmission links. The RF unit 414 may configure theantennas 416.

In an embodiment, the UE 400 can include multiple transceivers 410implementing different RATs (e.g., NR and LTE). In an embodiment, the UE400 can include a single transceiver 410 implementing multiple RATs(e.g., NR and LTE). In an embodiment, the transceiver 410 can includevarious components, where different combinations of components canimplement different RATs.

FIG. 5 is a block diagram of an exemplary BS 500 according toembodiments of the present disclosure. The BS 500 may be a BS 105 or BS205 as discussed above in FIGS. 1 and 3 , respectively. As shown, the BS500 may include a processor 502, a memory 504, a network slicing module508, a transceiver 510 including a modem subsystem 512 and a RF unit514, and one or more antennas 516. These elements may be in direct orindirect communication with each other, for example via one or morebuses.

The processor 502 may have various features as a specific-typeprocessor. For example, these may include a CPU, a DSP, an ASIC, acontroller, a FPGA device, another hardware device, a firmware device,or any combination thereof configured to perform the operationsdescribed herein. The processor 502 may also be implemented as acombination of computing devices, e.g., a combination of a DSP and amicroprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration.

The memory 504 may include a cache memory (e.g., a cache memory of theprocessor 502), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, asolid state memory device, one or more hard disk drives, memristor-basedarrays, other forms of volatile and non-volatile memory, or acombination of different types of memory. In some embodiments, thememory 504 may include a non-transitory computer-readable medium. Thememory 504 may store instructions 506. The instructions 506 may includeinstructions that, when executed by the processor 502, cause theprocessor 502 to perform operations described herein, for example,aspects of FIGS. 7-15 . Instructions 506 may also be referred to ascode, which may be interpreted broadly to include any type ofcomputer-readable statement(s) as discussed above with respect to FIG. 4.

The network slicing module 508 may be implemented via hardware,software, or combinations thereof. For example, the network slicingmodule 508 may be implemented as a processor, circuit, and/orinstructions 506 stored in the memory 504 and executed by the processor502. In some examples, the network slicing module 508 can be integratedwithin the modem subsystem 512. For example, the network slicing module508 can be implemented by a combination of software components (e.g.,executed by a DSP or a general processor) and hardware components (e.g.,logic gates and circuitry) within the modem subsystem 512.

The network slicing module 508 may be used for various aspects of thepresent disclosure, for example, aspects of FIGS. 7-15 . The networkslicing module 508 is configured to serve UEs (e.g., the UEs 115, 215,and/or 400) over a first cell frequency (e.g., the frequency carrier220), perform an association with a UE, and transmit, from the UE in thefirst cell frequency, a request for a particular network slice (e.g.,the network slices 250 and 252) of the network that is not supported inthe first cell frequency. The association can be based on a cellselection, a camping procedure, a random access procedure, a connectionset up procedure, and/or a network registration. The request can betransmitted in a NAS registration request message, a NAS service requestmessage, a NAS PDU session request message, an RRC service indicationmessage, or an on-demand SIB request message. The NAS registrationrequest message can include one or more requested network slices andpriorities of the requested network slices.

In an embodiment, the network slicing module 508 is configured to relay,to a core network entity (e.g., the core network 230), NAS messagesreceived from the UE and relay, to the UE, NAS messages received fromthe core network entity. In an embodiment, the network slicing module508 is configured to relay, to the core network entity, a NASregistration request message from the UE requesting one or more networkslices and receive, from the core network entity, an initial UE contextsetup requesting message indicating priorities of network slices thatare of interest to the UE. In an embodiment, the network slicing module508 is configured to relay, to the core network entity, a NAS servicerequest message from the UE requesting a network slice, and receive,from the core network entity, an initial UE context setup requestingmessage instructing the BS 500 to direct the UE to the second cellfrequency that includes the UE's requested network slice. In anembodiment, the network slicing module 508 is configured to receiveinformation associated with the UE's interested network slice and selecta target cell for a handover of the UE based on the UE's interestednetwork slice.

In an embodiment, the network slicing module 508 is configured totransmit, to the UE, an instruction to perform a handover to a secondcell frequency that supports the requested network slice and perform adual-connectivity with the second cell frequency, or perform a carrieraggregation with the second cell frequency to access the requested slicein the second cell frequency according to the instruction.

In an embodiment, the network slicing module 508 is configured toreceive, from the UE, an on-demand SIB request to request for frequencyto network slice mapping information for the interested network sliceand transmit slice-to-frequency mapping information for the networkslice based on upon the request from the UE. Mechanisms for performingmobility with network slicing consideration are described in greaterdetail herein.

As shown, the transceiver 510 may include the modem subsystem 512 andthe RF unit 514. The transceiver 510 can be configured to communicatebi-directionally with other devices, such as the UEs 115, 215, and/or400 and/or another core network element. The modem subsystem 512 may beconfigured to modulate and/or encode data according to a MCS, e.g., aLDPC coding scheme, a turbo coding scheme, a convolutional codingscheme, a digital beamforming scheme, etc. The RF unit 514 may beconfigured to process (e.g., perform analog to digital conversion ordigital to analog conversion, etc.) modulated/encoded data (e.g., NASmessages and/or RRC messages) from the modem subsystem 512 (on outboundtransmissions) or of transmissions originating from another source suchas a UE 115, 215, or 400. The RF unit 514 may be further configured toperform analog beamforming in conjunction with the digital beamforming.Although shown as integrated together in transceiver 510, the modemsubsystem 512 and/or the RF unit 514 may be separate devices that arecoupled together at the BS 105 to enable the BS 105 to communicate withother devices.

The RF unit 514 may provide the modulated and/or processed data, e.g.data packets (or, more generally, data messages that may contain one ormore data packets and other information), to the antennas 516 fortransmission to one or more other devices. This may include, forexample, transmission of information to complete attachment to a networkand communication with a camped UE 115, 215, or 400 according toembodiments of the present disclosure. The antennas 516 may furtherreceive data messages transmitted from other devices and provide thereceived data messages for processing and/or demodulation at thetransceiver 510. The transceiver 510 may provide the demodulated anddecoded data (e.g., NAS messages and/or RRC messages) to the networkslicing 508 for processing. The antennas 516 may include multipleantennas of similar or different designs in order to sustain multipletransmission links.

In an embodiment, the BS 500 can include multiple transceivers 510implementing different RATs (e.g., NR and LTE). In an embodiment, the BS500 can include a single transceiver 510 implementing multiple RATs(e.g., NR and LTE). In an embodiment, the transceiver 510 can includevarious components, where different combinations of components canimplement different RATs.

FIG. 6 illustrates a block diagram of an exemplary network unit 600according to embodiments of the present disclosure. The network unit 600may be a core network component of a core network such as the corenetwork 230 discussed above in FIG. 2 . A shown, the network unit 600may include a processor 602, a memory 604, a network slicing module 608,and a transceiver 610 including a modem subsystem 612 and a frontendunit 614. These elements may be in direct or indirect communication witheach other, for example via one or more buses.

The processor 602 may have various features as a specific-typeprocessor. For example, these may include a CPU, a DSP, an ASIC, acontroller, a FPGA device, another hardware device, a firmware device,or any combination thereof configured to perform the operationsdescribed herein. The processor 602 may also be implemented as acombination of computing devices, e.g., a combination of a DSP and amicroprocessor, a plurality of microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration.

The memory 604 may include a cache memory (e.g., a cache memory of theprocessor 602), RAM, MRAM, ROM, PROM, EPROM, EEPROM, flash memory, asolid state memory device, one or more hard disk drives, memristor-basedarrays, other forms of volatile and non-volatile memory, or acombination of different types of memory. In some embodiments, thememory 604 may include a non-transitory computer-readable medium. Thememory 604 may store instructions 606. The instructions 606 may includeinstructions that, when executed by the processor 602, cause theprocessor 602 to perform operations described herein. Instructions 606may also be referred to as code, which may be interpreted broadly toinclude any type of computer-readable statement(s) as discussed abovewith respect to FIG. 4 .

The network slicing module 608 may be implemented via hardware,software, or combinations thereof. For example, the network slicingmodule 608 may be implemented as a processor, circuit, and/orinstructions 606 stored in the memory 604 and executed by the processor602. The network slicing module 608 may be used for various aspects ofthe present disclosure, for example, aspects of FIGS. 7-15 . Forexample, the network slicing module 608 is configured to receive, from aUE (e.g., the UEs 115, 215, and/or 400) via a BS (e.g., the BSs 105,205, and/or 500, a NAS registration message requesting a network slice(e.g., the network slices 250 and 252) not supported by a cell frequency(e.g., the frequency carriers 220 and 222) that the UE is currentlycamped on or associated with, transmit, to the BS, an initial UE contextsetup request message based on the NAS registration message. The NASregistration message may indicate one or more network slices requestedby the UE and priorities of the requested network slices. The initial UEcontext setup request message can include the priorities of the UE'sinterested network slices. In an embodiment, the network slicing module608 is configured to receive, from the UE via the BS, a NAS servicerequest message requesting a network slice not supported by a cellfrequency that the UE is currently camped on or associated with andtransmit, to the BS, an initial UE context setup request messagerequesting the BS to switch the UE to a cell frequency that provides theUE's requested network slice. In an embodiment, the network slicingmodule 608 is configured to receive, from the UE via the BS, a PDUsession request message requesting a PDU session over a network slicenot supported by a cell frequency that the UE is currently camped on orassociated with and transmit, to the BS, a PDU session resource setupmessage to the BS. Mechanisms for facilitating network slice-awaremobility are described in greater detail herein.

As shown, the transceiver 610 may include the modem subsystem 612 andthe frontend unit 614. The transceiver 610 can be configured tocommunicate bi-directionally with other devices, such as the BSs 105,205, and 600 and/or another core network element. The modem subsystem612 may be configured to modulate and/or encode data according to a MCS,e.g., a LDPC coding scheme, a turbo coding scheme, a convolutionalcoding scheme, etc. The frontend unit 614 may includeelectrical-to-optical (E/O) components and/or optical-to-electrical(O/E) components that convert an electrical signal to an optical signalfor transmission to a BS such as the BSs 105, 210, and 220 and/orreceive an optical signal from the BS and convert the optical signalinto an electrical signal, respectively. The frontend unit 614 may beconfigured to process (e.g., perform analog to digital conversion ordigital to analog conversion, optical to electrical conversion orelectrical to optical conversion, etc.) modulated/encoded data from themodem subsystem 612 (on outbound transmissions) or of transmissionsoriginating from another source such as a backend or core network.Although shown as integrated together in transceiver 610, the modemsubsystem 612 and the frontend unit 614 may be separate devices that arecoupled together at the network unit 600 to enable the network unit 600to communicate with other devices. The frontend unit 614 may transmitoptical signal carrying the modulated and/or processed data over anoptical link such as the links 232. The frontend unit 614 may furtherreceive optical signals carrying data messages and provide the receiveddata messages for processing and/or demodulation at the transceiver 610.

FIGS. 7, 8, 9A, and 9B illustrate various mechanisms to a UE (e.g., theUEs 115, 215, and/or 400) with NAS signaling for indicating networkslice priorities and/or requesting a network slice that is not inallowed NSSAI. In other words, the requested network slice is notsupported by a cell frequency (e.g., the frequency carriers 220 and/or222) camped on by the UE or in a registered tracking area of the UE.

FIG. 7 is a signaling diagram illustrating a network slicingprovisioning method 700 according to some embodiments of the presentdisclosure. The method 700 may be implemented by a UE, a BS A, a BS B,and a core network. The UE may be similar to the UEs 115, 215, and/or400. The BS A and the BS B may be similar to the BSs 105, 205, and/or500. The BS A may operate over a frequency A (e.g., the frequencycarrier 220) supporting a network slice A (e.g., an eMBB slice similarto the slice 250). The BS B may operate over a frequency B (e.g., thefrequency carrier 222) supporting a network slice B (e.g., an URLLCslice similar to the slice 252). The core network may be similar to thecore network 230 and may include one or more network components to thenetwork unit 600. In an example, the core network may include an AMFcomponent (e.g., the network unit 600) that implements the method 700.As illustrated, the method 700 includes a number of enumerated steps,but embodiments of the method 700 may include additional steps before,after, and in between the enumerated steps. In some embodiments, one ormore of the enumerated steps may be omitted or performed in a differentorder.

At step 705, the UE is associated with frequency A, where slice B is notincluded in allowed NSSAI for frequency A. The UE may have performed arandom access procedure over the frequency A with the BS A.

At step 710, the UE receives a PDU session request on the slice B, forexample, initiated by an application requiring a service (e.g., an URLLCservice) on the slice B or by a higher layer operating system (OS) ofthe UE.

At step 715, the UE transmits a NAS registration request message to thecore network via the BS A. The registration request message may includerequested-NSSAI indicating the slice A and the slice B. The registrationrequest message may include a priority between the slice A and the sliceB. For example, the registration message may indicate that the slice Bhas a higher priority than slice A (denoted as B>A). In other words, theUE is more interested in receiving services from the slice B than fromthe slice A.

At step 720, the core network transmits an initial UE context setuprequest message to the BS A. For example, an AMF of the core network mayreject slice B, which is not supported over the frequency A. The initialUE context setup request message may include allowed NSSAI indicatingthe slice A and rejected NSSAI indicating the slice B. The initial UEcontext setup request message may indicate to the BS A that slice B hasa higher priority than slice A. The core network or the AMF may haveknowledge that the slice B is supported over the frequency B or the BSB. The initial UE context setup request message may provide instructionsfor the BS A to direct the UE to the frequency B that provides the sliceB.

At step 725, upon receiving the initial UE context setup request messagefrom the core network, the BS A transmits a NAS registration acceptmessage to the UE. At step 730, the BS A transmits an initial UE contextsetup response message to the core network accepting the initial UEcontext setup request.

At step 735, the BS A may instruct the UE to perform a handover to theBS B on the frequency B based on the AMF request (received in theinitial UE context setup request message). Alternatively, the BS A mayconfigure the UE for dual-connectivity or carrier aggregation to accessthe network slice B on the frequency B based on the AMF request. The UEmay perform the handover, dual-connectivity, or carrier aggregation asinstructed by the BS A and in coordination with the BS A, the BS B,and/or the core network. For dual-connectivity, the UE may continue tobe served by the BS A over the frequency A and additionally served bythe BS B over the frequency B. For carrier aggregation, the UE maycontinue to be served by the BS A over the frequency A and additionallyserved by the BS A over the frequency B.

At step 740, after performing a handover, a dual-connectivity, or acarrier aggregation to access the frequency B, the UE transmits anotherNAS registration request message to the core network via the BS B. TheNAS registration request message may include requested-NSSAI indicatingthe slice B and the slice A.

At step 745, in response to the NAS registration request message, thecore network transmits a NAS registration response message to the UE viathe BS B. The NAS registration response message may include allowedNSSAI indicating the slice B.

At step 750, the UE activates a PDU session over the slice B, forexample, in coordination with the BS B and the core network. The UE maytransmit a PDU session request to establish a PDU session over the sliceB. The UE may receive a PDU session response indicating a successfulestablishment of the PDU session.

FIG. 8 is a signaling diagram illustrating a network slicingprovisioning method 800 according to some embodiments of the presentdisclosure. The method 800 may be implemented by a UE, a BS A, a BS B,and a core network. The UE may be similar to the UEs 115, 215, and/or400. The BS A and the BS B may be similar to the BSs 105, 205, and/or500. The BS A may operate over a frequency A (e.g., the frequencycarrier 220) supporting a network slice A (e.g., an eMBB slice similarto the slice 250). The BS B may operate over a frequency B (e.g., thefrequency carrier 222) supporting a network slice B (e.g., an URLLCslice similar to the slice 252). The core network may be similar to thecore network 230 and may include one or more network components to thenetwork unit 600. In an example, the core network may include an AMFcomponent (e.g., the network unit 600) that implements the method 800.As illustrated, the method 800 includes a number of enumerated steps,but embodiments of the method 800 may include additional steps before,after, and in between the enumerated steps. In some embodiments, one ormore of the enumerated steps may be omitted or performed in a differentorder.

At step 805, the UE is associated with frequency A, where slice B is notincluded in allowed NSSAI for frequency A. The UE may have performed aNAS registration with the core network via the BS A over the frequencyA. In an example, the UE may have requested the slice A, but not theslice B during registration. In an example, the UE may have requestedthe slice A and the slice B, but may not have indicated that the slice Bhas a higher priority than the slice A.

At step 810, the UE receives a PDU session request on the slice B, forexample, initiated by an application requiring a service (e.g., an URLLCservice) on the slice B or by a higher layer OS of the UE.

At step 815, the UE transmits a NAS service request message to the corenetwork via the BS A. The NAS service request message may request forslice B.

At step 820, the core network transmits an initial UE context setuprequest message to the BS A. The initial UE context setup requestmessage may instruct the BS A to switch the UE to the frequency B whereslice B is provided. The initial UE context setup request message mayinclude a NAS service accept message.

At step 825, upon receiving the initial UE context setup request messagefrom the core network, the BS A transmits a NAS service accept messageto the UE. At step 830, the BS A transmits an initial UE context setupresponse message to the core network accepting the initial UE contextsetup request.

At step 835, the BS A may instruct the UE to perform a handover to theBS B on the frequency B based on the initial UE context setup request.Alternatively, the BS A may configure the UE for dual-connectivity orcarrier aggregation to access the network slice B on the frequency Bbased on the initial UE context setup request. The UE may perform thehandover, dual-connectivity, or carrier aggregation as instructed by theBS A and in coordination with the BS A, the BS B, and/or the corenetwork.

At step 840, after performing the handover, the dual-connectivity, orthe carrier aggregation to access the frequency B, the UE transmitsanother NAS registration request message to the core network via the BSB. The NAS registration request message may include requested-NSSAIindicating the slice B and the slice A.

At step 845, in response to the NAS registration request message, thecore network transmits a NAS registration response message to the UE viathe BS B. The NAS registration response message may include allowedNSSAI indicating the slice B.

At step 850, the UE activates a PDU session over the slice B, forexample, in coordination with the BS B and the core network. The UE maytransmit a PDU session request to establish a PDU session over the sliceB. The UE may receive a PDU session response indicating a successfulestablishment of the PDU session.

In an example, after completing the service on slice B, the UE mayrequest to return to slice A via a NAS service request in a similarmanner as shown by the steps 815-850 of the method 800.

FIGS. 9A and 9B are signaling diagrams that collective illustrates anetwork slice provisioning method 900 according to some embodiments ofthe present disclosure. The method 800 may be implemented by a UE, a BSA, a BS B, and a core network. The UE may be similar to the UEs 115,215, and/or 400. The BS A and the BS B may be similar to the BSs 105,205, and/or 500). The BS A may operate over a frequency A (e.g., thefrequency carrier 220) supporting a network slice A (e.g., an eMBB slicesimilar to the slice 250). The BS B may operate over a frequency B(e.g., the frequency carrier 222) supporting a network slice B (e.g., anURLLC slice similar to the slice 252). The core network may be similarto the core network 230 and may include one or more network componentsto the network unit 600. In an example, the core network may include anAMF component (e.g., the network unit 600) that implements the method900. As illustrated, the method 900 includes a number of enumeratedsteps, but embodiments of the method 900 may include additional stepsbefore, after, and in between the enumerated steps. In some embodiments,one or more of the enumerated steps may be omitted or performed in adifferent order.

Referring to FIG. 9A, at step 905, the UE is associated with frequencyA, where slice B is not included in allowed NSSAI for frequency A. TheUE may have performed a NAS registration with the core network via theBS A over the frequency A. In an example, the UE may have requested theslice A, but not the slice B during registration. In an example, the UEmay have requested the slice A and the slice B, but may not haveindicated that the slice B has a higher priority than the slice A.

At step 910, the UE receives a PDU session request on the slice B, forexample, initiated by an application requiring a service (e.g., an URLLCservice) on the slice B or by a higher layer OS of the UE.

At step 915, the UE transmits a PDU session request message to the corenetwork via the BS A. The PDU session request message may request forslice B. In an example, the UE may transmit the PDU session request forthe slice B when the E determines that the slice B has a higher prioritythan the slice A and/or determines that the slice B in a coverage area(e.g., the area 210) of a cell frequency providing the slice B base onmeasurement information and/or received system information (e.g., fromprevious SIB reception or registration).

At step 920, the core network transmits a PDU session resource setuprequest message to the BS A. The PDU session resource setup requestmessage may request the BS A to setup resources for slice B.

At step 925, in response to the PDU session resource setup requestmessage, the BS A transmits a PDU session resource setup responsemessage to the core network. The PDU session resource setup responsemessage may indicate a failure since the BS A does not support the sliceB over the frequency A. The PDU session resource setup response messagemay indicate a cause or reason for the failure and indicate that ahandover trigger is required.

At step 930, the BS A may instruct the UE to perform a handover orredirection to the BS B on the frequency B. The UE may perform thehandover as instructed by the BS A and in coordination with the BS A,the BS B, and/or the core network. In some instances, the redirectionmay refer to a radio resource control (RRC) release with redirection.

Referring to FIG. 9B, at step 935, after performing the handover, thedual-connectivity, or the carrier aggregation to access the frequency B,the UE transmits another NAS registration request message to the corenetwork via the BS B. The NAS registration request message may includerequested-NSSAI indicating the slice B and the slice A.

At step 940, in response to the NAS registration request message, thecore network transmits a NAS registration response message to the UE viathe BS B. The NAS registration response message may include allowedNSSAI indicating the slice B.

At step 945, the core network transmits a PDU session resource setuprequest message to the BS B. The PDU session resource setup requestmessage may request the BS B to setup resources for slice B.

At step 950, in response to the PDU session resource setup requestmessage, the BS B transmits a PDU session resource setup responsemessage to the core network. The PDU session resource setup responsemessage may indicate a success or completion of the resource setup.

At step 955, upon receiving the PDU session resource setup responsemessage, the core network transmits a PDU session response message tothe UE via the BS B. The PDU session resource setup response message mayindicate a successful completion of the PDU session establishment.

At step 960, upon receiving the PDU session response message with asuccess from the core network, the UE may respond to the application orthe OS with a PDU session setup success. Subsequently, the UE (or theapplication) may execute a service (e.g., the URLLC service) over thePDU session on the slice B.

In an example, when the handover or redirection of the UE to thefrequency B in the step 930 fails, the core network may still accept thePDU session on the slice B, but may keep the PDU session on the slice Bin a dormant state (e.g., an inactive state). The UE may activate thePDU session via a NAS service request at a later time.

As can be observed from the method 900, the method 900 allows a UE torequest for a PDU session on a network slice (e.g., the network slice250) that is not in allowed NSSAI.

FIG. 10 is a signaling diagram illustrating a network slicingprovisioning method 1000 according to some embodiments of the presentdisclosure. The method 1000 may be implemented a UE, a BS A, a BS B, anda core network. The UE may be similar to the UEs 115, 215, and/or 400.The BS A and the BS B may be similar to the BSs 105, 205, and/or 500.The BS A may operate over a frequency A (e.g., the frequency carrier220) supporting a network slice A (e.g., an eMBB slice similar to theslice 250). The BS B may operate over a frequency B (e.g., the frequencycarrier 222) supporting a network slice B (e.g., an URLLC slice similarto the slice 252). The core network may be similar to the core network230 and may include one or more network components to the network unit600. In an example, the core network may include an AMF component (e.g.,the network unit 600) that implements the method 1000. As illustrated,the method 1000 includes a number of enumerated steps, but embodimentsof the method 1000 may include additional steps before, after, and inbetween the enumerated steps. In some embodiments, one or more of theenumerated steps may be omitted or performed in a different order.Similar to the methods 700, 800, and/or 900, the method 1000 allows a UEto request a network slice that is not in allowed NSSAI. However, themethod 1000 utilizes RRC signaling instead of NAS signaling.

At step 1005, the UE is associated with frequency A, where slice B isnot included in allowed NSSAI for frequency A. The UE may have performeda NAS registration with the core network via the BS A over the frequencyA. In an example, the UE may have requested the slice A, but not theslice B during registration. In an example, the UE may have requestedthe slice A and the slice B, but may not have indicated that the slice Bhas a higher priority than the slice A.

At step 1010, the UE receives a PDU session request on the slice B, forexample, initiated by an application requiring a service (e.g., an URLLCservice) on the slice B or by a higher layer OS of the UE.

At step 1015, the UE transmits a service interest indication message tothe BS A. The service interest indication message may indicate the sliceB. In an example, the service interest indication message may include alist of UE interested network slices and/or priorities of the networkslices. In an example, that the service interest indication message mayinclude a list of UE interested frequencies (e.g., the frequencycarriers 220 and 222). In an example, the service interest indicationmessage may include a list of UE interested network slices, prioritiesof the network slices, and/or the list of UE interested frequencies. Theservice interest indication message is a RRC message e.g., a RRCmultimedia broadcast multicast serve (MBMS) message).

At step 1020, upon receiving the service interest indication message,the BS A may instruct the UE to perform a handover to the BS B on thefrequency B where the slice B is served. The UE may perform the handoverto the BS B as instructed by the BS A and in coordination with the BS A,the BS B, and/or the core network.

At step 1025, after performing the handover to the frequency B, the UEtransmits another NAS registration request message to the core networkvia the BS B. The NAS registration request message may includerequested-NSSAI indicating the slice B and the slice A.

At step 1030, in response to the NAS registration request message, thecore network transmits a NAS registration response message to the UE viathe BS B. The NAS registration response message may include allowedNSSAI indicating the slice B.

At step 1035, the UE activates a PDU session over the slice B, forexample, in coordination with the BS B and the core network. The UE maytransmit a PDU session request to establish a PDU session over the sliceB. The UE may receive a PDU session response indicating a successfulestablishment of the PDU session.

At step 1040, after activating the PDU session over the slice B, the UEmay respond to the application or the OS with a PDU session activated.Subsequently, the UE (or the application) may execute a service (e.g.,the URLLC service) over the PDU session on the slice B.

In an example, during an RRC release or RRC resume, the BS may assigndedicated priority based on UE interested slices and/or frequenciesreceived from the RRC service interest indication message. For example,the dedicated priority may include frequency priority information thatthe UE may use during cell reselection while the UE is in an RRC idlestate and/or RRC inactive state. The frequency priority information maybe included in the RRC release message. Additionally, the BS may takethe UE's interested slices into consideration for performing mobility(e.g., target cell selection) while the UE is in an RRC connected state.

FIG. 11 is a signaling diagram illustrating a network slicingprovisioning method 1100 according to some embodiments of the presentdisclosure. The method 1100 may be implemented a UE, a BS A, and a corenetwork. The UE may be similar to the UEs 115, 215, and/or 400. The BS Amay be similar to the BSs 105, 205, and/or 500. The BS A may operateover a frequency A (e.g., the frequency carrier 220) supporting anetwork slice A (e.g., an eMBB slice similar to the slice 250). Anetwork slice B (e.g., an URLLC slice similar to the slice 252) may besupported over a frequency B (e.g., the frequency carrier 222) differentform the frequency A. The core network may be similar to the corenetwork 230 and may include one or more network components to thenetwork unit 600. In an example, the core network may include an AMFcomponent (e.g., the network unit 600) that implements the method 1100.As illustrated, the method 1100 includes a number of enumerated steps,but embodiments of the method 1100 may include additional steps before,after, and in between the enumerated steps. In some embodiments, one ormore of the enumerated steps may be omitted or performed in a differentorder. The method 1100 may be used in conjunction with the method 700and/or 800 as described above with respect to FIGS. 7 and 8 ,respectively. The method 1100 provides a more detailed view forsupporting a network slice that is not in allowed NSSAI viadual-connectivity and/or carrier aggregation.

At step 1105, the UE is associated with frequency A, where slice B isnot included in allowed NSSAI for frequency A. The UE may have performeda NAS registration with the core network via the BS A over the frequencyA. In an example, the UE may have requested the slice A, but not theslice B during registration. In an example, the UE may have requestedthe slice A and the slice B, but may not have indicated that the slice Bhas a higher priority than the slice A.

At step 1110, the BS A receives a request for the slice B. In anexample, the slice B request may be initiated by the UE (e.g., based onthe UE receiving a request for the slice B from higher layer applicationor a service of the UE). In an example, the slice B request may beinitiated by the core network. In general, the slice B request can beinitiated by any entity in the network.

At step 1115, the BS A may configure the UE with a secondary cell(SCell) B over the frequency B via dual-connectivity or carrieraggregation. The UE may perform the dual-connectivity or carrieraggregation to access the S Cell on the frequency B. The frequency A maybe referred to as a primary cell (PCell)

At step 1120, after performing the dual-connectivity or carrieraggregation, the UE transmits a NAS registration request message to thecore network, for example, via the SCell. The NAS registration requestmessage may include requested-NSSAI indicating the slice B and the sliceA.

At step 1125, in response to the NAS registration request message, thecore network transmits a NAS registration response message to the UE forexample, via the SCell. The NAS registration response message mayinclude allowed NSSAI indicating the slice B.

At step 1130, the UE activates a PDU session over the slice B. The UEmay transmit a PDU session request to establish a PDU session over theslice B. The UE may receive a PDU session response indicating asuccessful establishment of the PDU session. Subsequently, the UE may beserved a service (e.g., an URLLC service) in the PDU session over theslice B in the SCell.

After some time, at step 1135, the BS A may de-configure thedual-connectivity or carrier aggregation. In other words, the BS Ade-configure the UE from being served by the SCell on the frequency B.

At step 1140, after the de-configuration, the UE transmits another NASregistration request message to the core network, for example, via thePCell on the frequency A. The NAS registration request message mayinclude requested-NSSAI indicating the slice A and the slice B.

At step 1145, in response to the NAS registration request message, thecore network transmits a NAS registration response message to the UE forexample, via the PCell on the frequency A. The NAS registration responsemessage may include allowed NSSAI indicating the slice A.

In an example, when the UE detects that a dual-connectivity or carrieraggregation configuration or de-configuration may impact network slicesupport capability or status change, the UE may initiate a NASregistration to update allowed NSSAI. As shown above, at the step 1105,the UE may have stored allowed NSSAI indicating the slice A. After thedual-connectivity or carrier aggregation configuration at step 1115, theUE initiated a NAS registration and obtained updated allowed NSSAIindicating the slice B. After the dual-connectivity or carrieraggregation de-configuration at step 1135, the UE initiated a NASregistration and obtained updated allowed NSSAI indicating the slice A.In an example, the network may configure the UE to trigger a NASregistration after a dual-connectivity or carrier aggregationconfiguration and/or after a dual-connectivity or carrier aggregationde-configuration so that the UE may obtained updated allowed NSSAIincluding the slice B.

In some examples, when the RAN (e.g., the BS A) determines that theavailability status of the UE's interested network slice may changeafter a dual-connectivity or carrier aggregation configuration (e.g., atthe step 1115) or after a dual-connectivity or carrier aggregationde-configuration (e.g., at the step 1135), the RAN may indicate to thecore network that the availability status of the UE's interested slicehas changed so that the core network may update the allowed NSSAI.

In an example, if the UE requested multiple slices (e.g., the slices 250and 252) or frequencies (e.g., the frequency carriers 220 and 222) thatmay be supported by a single cell, the BS may attempt to meet therequest by configuring the UE with multiple SCells throughdual-connectivity or carrier aggregation. If dual-connectivity orcarrier aggregation with SCells does not meet the request, the BS mayredirect or handover the UE to a frequency that supports a highestpriority network slice (that the UE is most interested in).

FIG. 12 is a signaling diagram illustrating a network slicingprovisioning method 1200 according to some embodiments of the presentdisclosure. The method 1200 may be implemented by a UE, a BS A, a BS B,and a core network. The UE may be similar to the UEs 115, 215, and/or400. The BS A and the BS B may be similar to the BSs 105, 205, and/or500. The BS A may operate over a frequency A (e.g., the frequencycarrier 220) supporting a network slice A (e.g., an eMBB slice similarto the slice 250). The BS B may operate over a frequency B (e.g., thefrequency carrier 222) supporting a network slice B (e.g., an URLLCslice similar to the slice 252). The core network may be similar to thecore network 230 and may include one or more network components to thenetwork unit 600. In an example, the core network may include an AMFcomponent (e.g., the network unit 600) that implements the method 1200.As illustrated, the method 1200 includes a number of enumerated steps,but embodiments of the method 1200 may include additional steps before,after, and in between the enumerated steps. In some embodiments, one ormore of the enumerated steps may be omitted or performed in a differentorder. The method 1200 provides network slice-to-frequency mapping viaan on-demand SIB request.

At step 1205, the UE is camped on frequency A, where slice B is notincluded in allowed NSSAI for frequency A. In an example, the UE may bein an RRC idle mode. The UE may have received system information (e.g.,SIBs) from the BS A. The UE may have received allowed NSSAI for thecurrently camped frequency A (e.g., from a previous connection to thenetwork and/or previous monitoring).

At step 1210, the UE receives a PDU session request on the slice B, forexample, initiated by an application requiring a service (e.g., an URLLCservice) on the slice B or by a higher layer OS of the UE.

At step 1215, the UE transmits a SIB request message in the frequency Ato the BS A. The SIB request may request for information (e.g.,slice-to-frequency mapping information) for the slice B. For example,the UE determines that the slice B is not in the current allowed NSSAI(e.g., over the currently camped frequency A). The UE may transmit theSIB request message via a random access procedure. For example, the UEmay transmit the SIB request message in a MSG 1, MSG 3, or a MSG A.

At step 1220, in response to the SIB request, the BS A transmits a SIBresponse message indicating slice B information, for example, indicatingthe frequency B where the slice B is supported. In an example, the BSmay transmit the SIB response message via a MSG 2, MSG 4, or a MSG B. Inan example, a SIB with slice-to-frequency mapping may be too large to betransmitted over the air interface. The BS A may include a subset of theslice-to-frequency mapping SIB in the SIB response message.

At step 1225, after receiving the frequency mapping information for theslice B, the UE performs a cell reselection to reselect to the frequencyB. The UE may perform an RRC connection setup with the BS B based on thereselection to the frequency B. The RRC connection setup may include theexchange of random access messages (e.g., the four-step random access orthe two-step random access)

At step 1230, after reselecting to the frequency B and performing theRRC connection setup, the UE transmits another NAS registration requestmessage to the core network via the BS B. The NAS registration requestmessage may include requested-NSSAI indicating the slice B and the sliceA.

At step 1235, in response to the NAS registration request message, thecore network transmits a NAS registration response message to the UE viathe BS B. The NAS registration response message may include allowedNSSAI indicating the slice B.

At step 1240, the UE activates a PDU session over the slice B, forexample, in coordination with the BS B and the core network. The UE maytransmit a PDU session request to establish a PDU session over the sliceB. The UE may receive a PDU session response indicating a successfulestablishment of the PDU session.

At step 1245, after activating the PDU session over the slice B, the UEmay respond to the application or the OS with a PDU session activated.Subsequently, the UE (or the application) may execute a service (e.g.,the URLLC service) over the PDU session on the slice B.

As can be observed form the method 1200, the UE may perform cellreselection based on based on a service requirement. The UE may takeinterested network slices into consideration for cell reselection. Forexample, when the UE is interested in an URLLC service and an URLLCslice (e.g., the slice 252) in not allowed in the currently campedfrequency, the UE may reselect to a cell frequency (e.g., the frequencycarrier 222) that supports an URLLC slice. Alternatively, when the UE isinterested in an eMBB service (e.g., the frequency carrier 222) and aneMBB slice (e.g., the slice 250) in not allowed in the currently campedfrequency, the UE may reselect to a cell frequency that supports an eMBBslice. The UE can request a BS on a currently camped cell to provideadditional SIB on demand based on an initiation from an application. Inother words, the UE can perform BS assisted service cell reselection.While the method 1200 is described in the context of cell reselection,the UE may perform a service-based BS-assisted cell selection usingsubstantially similar mechanisms as in the method 1200.

FIGS. 13A and 13B collectively illustrate mechanisms for performing anetwork slice-aware mobility. FIG. 13A illustrates a handover scenario1300 with network slicing according to some embodiments of the presentdisclosure. FIG. 13B is a signaling diagram illustrating a networkslice-aware handover method 1310 according to some embodiments of thepresent disclosure.

Referring to FIG. 13A, the handover scenario 1300 may correspond to ascenario in the network 100. In the handover scenario 1300, a cell 1306a (denoted as Cell 1) operates over a carrier frequency F1 (e.g., thefrequency carrier 220) in a tracking area T1 and provides a slice S1(e.g., an eMBB slice similar to the slice 250). A cell 1306 b (denotedas Cell 3) operates over a carrier frequency F2 (e.g., the frequencycarrier 222) in the tracking area T2 and provides a slice S1 and a sliceS2 (e.g., an URLLC slice similar to the slice 252). A cell 1306 b(denoted as Cell 2) also operates over the carrier frequency F1 in thetracking area T1 and provides a slice S1. The cell 1306 a may beoperated by a BS 1304 a, the cell 1306 b may be operated by a BS 1304 b,and the cell 1306 c may be operated by a BS 1304 c. The BSs 1304 a, 1304b, and 1304 c may be substantially similar to the BSs 105, 205, and/or500.

A UE 1302 (e.g., the UEs 115, 215, and/or 500) may be camped on the cell1306 a. The UE 1302 may be interested in a slice S1 and a slice S2. TheBS 1304 a may be provided with information related to the UE's interestin slice S1 and slice S2 as described in greater detail below in themethod 1310. Accordingly, the BS 1304 a may handover the UE 1302 to thecell 1306 b (shown by the dashed arrow 1308) instead of the cell 1306 cbased on the UE's network slice interest information. The BS 1304 a mayselect the cell 1306 b based on a match of the UE's interested slice S1and slice S2 to the slice S1 and slice S2 supported by the frequency F2over the cell 1306 b.

Referring to FIG. 13B, the method 1310 may be implemented by the UE1302, the BS 1304 a, and a core network. The core network may be similarto the core network 230 and may include one or more network componentsto the network unit 600. In an example, the core network may include anAMF component (e.g., the network unit 600) that implements the method1310. The method 1310 illustrates the signaling for providing the BS1304 a with the UE 1302's network slice interest for network slice-awaremobility. As illustrated, the method 1310 includes a number ofenumerated steps, but embodiments of the method 1310 may includeadditional steps before, after, and in between the enumerated steps. Insome embodiments, one or more of the enumerated steps may be omitted orperformed in a different order.

At step 1315, the UE 1302 enters cell 1 (e.g., the cell 1306 a) in thetracking area T1. The UE 1302 is interested in a slice S1 (e.g., an eMBBslice) and a slice S2 (e.g., an URLLC slice).

At step 1320, the UE 1302 transmits a NAS registration request messageto the AMF via the BS 1304 a. The NAS registration request message mayinclude requested-NSSAI indicating a slice S1 and a slice S2.

At step 1325, the AMF determines that the slice S2 in therequested-NSSAI is not supported in the current tracking area T1.

At step 1330, the AMF transmits an initial UE context setup requestmessage to the BS 1304 a. The initial UE context setup request messagemay include allowed NSSAI, rejected NSSAI, and a rejection cause. Theallowed NSSAI may indicate the slice 1. The rejected NSSAI may indicatethe slice S2. The rejection cause may indicate a reason for rejectingthe slice S2. For example, the rejection cause may indicate that thecurrent PLMN does not support the requested slice S2. Alternatively, therejection cause may indicate that the current registration area (e.g.,the registered tracking area) does not support the requested slice S2.

At step 1335, the AMF transmits a NAS registration accept message to theUE 1302 via the BS 1304 a. The NAS registration accept message mayinclude allowed NSSAI indicating the slice S1 and rejected NSSAIindicating the slice S2.

At step 1340, based on the rejection cause provided by the AMF in theinitial UE context setup request message, the BS 1304 a prioritizesfrequency (e.g., the frequency F2) with support for the slices S1 and S2for performing mobility for the UE 1302. For example, as shown in thescenario 1300, the BS 1304 a handover the UE 1302 to the cell 1306 b.The BS 1304 a may direct the UE 1302 to the cell 1306 a

At step 1345, the UE 1302 performs handover to the cell 1306 b. At step1350, the UE 1302 may start or execute an application (denoted as App X)over the slice S2 with a success since the cell 1306 b provides theslice.

As can be observed in the method 1310, the AMF (or the core network)transmits rejected NSSAI as well as the cause of the rejection to the BS1304 a (or the RAN). The rejected NSSAI and the rejection cause providesthe RAN with information associated with information associated with aUE 1302's interested network slices. Accordingly, the BS 1304 a or theRAN can support network slice-aware mobility. The network slice-awaremobility can provide the UE 1302 with dynamic slice request and a fasteracquisition of a cell frequency that can provide a slice required by theUE.

FIG. 14 is a flow diagram of a communication method 1400 according tosome embodiments of the present disclosure. Steps of the method 1400 canbe executed by a computing device (e.g., a processor, processingcircuit, and/or other suitable component) of a wireless communicationdevice or other suitable means for performing the steps. For example, awireless communication device, such as the UE 115, UE 215, UE 400,and/or UE 1302, may utilize one or more components, such as theprocessor 402, the memory 404, the network slicing module 408, thetransceiver 410, the modem 412, and the one or more antennas 416, toexecute the steps of method 1400. The method 1400 may employ similarmechanisms as in the methods 700, 800, 900, 1000, 1200, and/or 1310described above with respect to FIGS. 7, 8, 9, 10, 11, 12 , and/or 13,respectively. As illustrated, the method 1400 includes a number ofenumerated steps, but embodiments of the method 1400 include additionalsteps before, after, and in between the enumerated steps. In someembodiments, one or more of the enumerated steps may be omitted orperformed in a different order.

At step 1410, the method 1400 includes transmitting, by the UE in afirst cell frequency (e.g., the frequency carrier 220) a network (e.g.,the networks 100 and/or 200), a request for a network slice (e.g., thenetwork slice 252) of the network that is not provided by the first cellfrequency.

At step 1420, the method 1400 includes receiving, by the UE in responseto the request, information for communicating in a second cell frequency(e.g., the frequency carrier 222) of the network that provides thenetwork slice requested.

In an embodiment, the transmitting includes transmitting, by the UE, aNAS registration request message including NSSAI, where the NSSAIindicates that the network slice requested is preferred over anothernetwork slice of the network, for example, as shown in the method 700.

In an embodiment, the transmitting includes transmitting, by the UE, aNAS service request message indicating the network slice that is not inallowed NSSAI (e.g., received during a NAS registration), for example,as shown in the method 800.

In an embodiment, the transmitting includes transmitting, by the UE, aPDU session request message indicating the network slice that is not inallowed NSSAI (e.g., received during a NAS registration), for example,as shown in the method 900.

In an embodiment, the transmitting includes transmitting, by the UE, anRRC message indicating an interest for the network slice, for example,as shown in the method 1000.

In an embodiment, the transmitting includes transmitting, by the UE, asystem information request message requesting frequency informationassociated with the network slice. The receiving includes receiving, bythe UE, a system information response message including the frequencyinformation indicating that the network slice is provided by the secondcell frequency, for example, as shown in the method 1200.

In an embodiment, the receiving includes receiving, by the UE, aninstruction to perform at least one of a handover to the second cellfrequency. In an embodiment, the receiving includes receiving, by theUE, an instruction to perform a dual-connectivity with the second cellfrequency. In an embodiment, the receiving includes receiving, by theUE, an instruction to perform a carrier aggregation with the second cellfrequency.

FIG. 15 is a flow diagram of a communication method 1500 according tosome embodiments of the present disclosure. Steps of the method 1500 canbe executed by a computing device (e.g., a processor, processingcircuit, and/or other suitable component) of a wireless communicationdevice or other suitable means for performing the steps. For example, anetwork entity, such as the BS 105, 205, 500, and/or 1304, may utilizeone or more components, such as the processor 502, the memory 504, thenetwork slicing module 508, the transceiver 510, the modem 512, and theone or more antennas 516, to execute the steps of method 1500.Alternatively, a network entity, such as a core network 230 and/or thenetwork unit 600, may utilize one or more components, such as theprocessor 602, the memory 604, the network slicing module 608, thetransceiver 610, the modem 612, and the frontend 614, to execute thesteps of method 1500. The method 1500 may employ similar mechanisms asin the methods 700, 800, 900, 1000, 1200, and/or 1310 described abovewith respect to FIGS. 7, 8, 9, 10, 11, 12 , and/or 13, respectively. Asillustrated, the method 1500 includes a number of enumerated steps, butembodiments of the method 1500 include additional steps before, after,and in between the enumerated steps. In some embodiments, one or more ofthe enumerated steps may be omitted or performed in a different order.

At step 1510, the method 1500 includes receiving, by a network entityfrom a UE (e.g., the UEs 115, 215, 400, and/or 1302) in a first cellfrequency (e.g., the frequency carrier 220) of a network (e.g., thenetworks 100 and/or 200), a request for a network slice (e.g., thenetwork slice 252) of the network, the network slice not provided by thefirst cell frequency.

At step 1520, the method 1500 includes transmitting, by the networkentity to the UE, information for communicating in a second cellfrequency (e.g., the frequency carrier 222) of the network providing thenetwork slice.

In an embodiment, the receiving includes receiving, by the networkentity from the UE, a NAS registration request message including NSSAI,the NSSAI indicating that the network slice requested is preferred overanother network slice of the network, for example, as shown in themethod 700. In an embodiment, the network entity may correspond to a BS(e.g., the BSs 105, 205, 500, and/or 1304). In such an embodiment, thenetwork entity may relay, to a core network entity (e.g., the corenetwork 230) of the network, the request and receive, from the corenetwork entity, a message indicating that the UE prefers the networkslice requested over the another network slice. In an embodiment, thenetwork entity may be a core network entity (e.g., the core network230). In such an embodiment, the receiving includes receiving, by thenetwork entity, the request via a BS (e.g., the BSs 105, 205, 500,and/or 1304) operating over the first cell frequency and the networkentity may transmit, to the BS, a message indicating that the UE prefersthe network slice requested over the another network slice.

In an embodiment, the receiving includes receiving, by the networkentity from the UE, a NAS service request message indicating the networkslice that is not included in allowed NSSAI of the first cell frequency,for example, as shown in the method 800. In an embodiment, the networkthe network entity may correspond to a BS (e.g., the BSs 105, 205, 500,and/or 1304) and may relay, to a core network entity (e.g., the corenetwork 230) of the network, the request, The network entity mayreceive, from the core network entity, an instruction to switch the UEto the second cell frequency. In an embodiment, the network entity maybe a core network entity (e.g., the core network 230) and receive therequest via a base station (BS) operating over the first cell frequency.The network entity may further transmit, to the BS, an instruction toswitch the UE to the second cell frequency.

In an embodiment, the receiving includes receiving, by the networkentity from the UE, a PDU session request message indicating the networkslice that is not included in allowed NSSAI of the first cell frequency,for example, as shown in the method 900.

In an embodiment, the receiving includes receiving, by the networkentity from the UE, an RRC message indicating an interest for thenetwork slice, for example, as shown in the method 1000.

In an embodiment, the receiving includes receiving, by the networkentity, a system information request message requesting frequencyinformation associated with the network slice. The network entityfurther transmits a system information response message (e.g., a SIB)indicating that the network slice is provided by the second cellfrequency, for example, as shown in the method 1200.

In an embodiment, the transmitting includes transmitting, by the networkentity, an instruction to perform at least one of a handover to thesecond cell frequency. In an embodiment, the transmitting includestransmitting, by the network entity, an instruction to perform adual-connectivity with the second cell frequency. In an embodiment, thetransmitting includes transmitting, by the network entity, aninstruction to perform a carrier aggregation with the second cellfrequency.

FIG. 16 is a flow diagram of a communication method 1600 according tosome embodiments of the present disclosure. Steps of the method 1600 canbe executed by a computing device (e.g., a processor, processingcircuit, and/or other suitable component) of a wireless communicationdevice or other suitable means for performing the steps. For example, acore network entity, such as a core network 230 and/or the network unit600, may utilize one or more components, such as the processor 602, thememory 604, the network slicing module 608, the transceiver 610, themodem 612, and the frontend 614, to execute the steps of method 1600.The method 1600 may employ similar mechanisms as in the methods 700,800, 900, 1000, 1200, 1310, and/or 1500 described above with respect toFIGS. 7, 8, 9, 10, 11, 12, 13 , and/or 15, respectively. As illustrated,the method 1600 includes a number of enumerated steps, but embodimentsof the method 1600 include additional steps before, after, and inbetween the enumerated steps. In some embodiments, one or more of theenumerated steps may be omitted or performed in a different order.

At step 1610, the method 1600 includes receiving, by a core networkentity from a BS (e.g., the BSs 105, 205, and/or 500) operating over afirst cell frequency (e.g., the frequency carrier 220) of the network(e.g., the networks 100 and/or 200), a request to provide a networkslice (e.g., the network slice 252) of a network (e.g., the networks 100and/or 200) to a UE (e.g., the UEs 115, 215, 400, and/or 1302), thenetwork slice not provided by the first cell frequency.

At step 1620, the method 1600 includes transmitting, by the core networkentity to the BS, information associated with a second cell frequency(e.g., the frequency carrier 222) of the network providing the networkslice.

FIG. 17 is a flow diagram of a communication method 1700 according tosome embodiments of the present disclosure. Steps of the method 1700 canbe executed by a computing device (e.g., a processor, processingcircuit, and/or other suitable component) of a wireless communicationdevice or other suitable means for performing the steps. For example, anetwork entity, such as the BS 105, 205, 500, and/or 1304, may utilizeone or more components, such as the processor 502, the memory 504, thenetwork slicing module 508, the transceiver 510, the modem 512, and theone or more antennas 516, to execute the steps of method 1700. Themethod 1700 may employ similar mechanisms as in the methods 700, 800,900, 1000, 1200, 1310, and/or 1500 described above with respect to FIGS.7, 8, 9, 10, 11, 12, 13 , and/or 15, respectively. As illustrated, themethod 1700 includes a number of enumerated steps, but embodiments ofthe method 1700 include additional steps before, after, and in betweenthe enumerated steps. In some embodiments, one or more of the enumeratedsteps may be omitted or performed in a different order.

At step 1710, the method 1700 includes obtaining, by the BS, anindication that a UE (e.g., the UEs 115, 215, 400, and/or 1302) isinterested in a network slice (e.g., the network slice 252) of a network(e.g., the networks 100 and/or 200) not provided by a first cellfrequency (e.g., the frequency carrier 220), the BS in communicationwith the UE in the first cell frequency.

At step 1720, the method 1700 includes receiving, by the BS from a corenetwork entity, information associated with a second cell frequency(e.g., the frequency carrier 222) of the network providing the networkslice.

FIG. 18 illustrates an example call flow diagram of a network thatsupports mobility that considers network slicing factors, in accordancewith certain aspects of the present disclosure. For instance, thenetwork may be similar to the network 100 of FIG. 1 and/or network 200of FIG. 2 . As illustrated in FIG. 18 , in some cases, a UE may indicateinterested slices by a new RRC message. For example, the new RRC messagemay be referred to as a new RRC message Service Interest Indication withvarious optional parameters. The optional parameters may include one ormore of an interested frequency list, a single NSSAI (S-NSSAI) list, aTemporary Mobile Group Identity (TMGI) list, and relative prioritybetween services. The UE may be similar to the UEs 115, 215, 400, and/or1302 discussed above in relation to FIGS. 1, 2, 4 , and/or 13,respectively.

In some cases, to allow a UE to identify what cells support whatservices, Service-Frequency mapping info may be provided to the UE. Suchinformation may be provided via a SIB. As an alternative, suchinformation could be provided by user plane (e.g., a download from aURL, similar to a User Service Description download in MBMS). In suchcases, a version tag may be broadcasted in SIB for UE to check thefreshness of its cached or fetched information. As described above, theRAN (e.g., the RAN 240) may also get “subscribed NSSAI” info from AMF toverify which of the UE requested slices are valid.

According to another option, the 5GC (e.g., the core network 230) mayindicate UE interested slices to RAN (based on information provided bythe UE). For example, the UE may provide “Requested NSSAI” to AMF in NASRegistration Request. The UE interested NSSAI should be included in theNAS “Requested NSSAI.” The 5GC may then send the Interested NSSAI toRAN. The “S-NSSAIs” not in “Subscribed NSSAI” may be excluded fromInterested NSSAI. In some cases (e.g., due to security/privacyconcerns), the “Requested NSSAI” in Msg5 may not include full set of UEinterested slices.

According to another option, the UE may send a PDU Session Request for aslice outside of “Allowed NSSAI” as an implicit indication of aninterested slice. For example, when a request for slice X (which isoutside of “Allowed NSSAI”) is received, the UE may send out a PDUSession Request for slice X, if the UE believes it is still in thecoverage of slice X.

The UE may know/believe it is slice X coverage, for example, based onmeasurement (e.g., UE is in gNB coverage), stored information (e.g., gNBsupports slice X), SIB, or other information as described above. The gNBmay be similar to the BSs 105, 205, 500, and/or 1304 discussed above inrelation to FIGS. 1, 2, 5 , and/or 13, respectively.

When PDU Session Request for slice X is received, the 5GC may sendtentative PDU Session Establishment Request to the RAN. The RAN may thenhandover the UE to cell supporting slice X if possible.

As described herein, aspects of the present disclosure provideenhancements for Slice-aware mobility based on UE Interested Sliceswhich may help avoid a UE being handed over to a cell that does notsupport a slice of interest when it was, in fact, in coverage area ofthat slice.

Information and signals may be represented using any of a variety ofdifferent technologies and techniques. For example, data, instructions,commands, information, signals, bits, symbols, and chips that may bereferenced throughout the above description may be represented byvoltages, currents, electromagnetic waves, magnetic fields or particles,optical fields or particles, or any combination thereof.

The various illustrative blocks and modules described in connection withthe disclosure herein may be implemented or performed with ageneral-purpose processor, a DSP, an ASIC, an FPGA or other programmablelogic device, discrete gate or transistor logic, discrete hardwarecomponents, or any combination thereof designed to perform the functionsdescribed herein. A general-purpose processor may be a microprocessor,but in the alternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices (e.g., a combinationof a DSP and a microprocessor, multiple microprocessors, one or moremicroprocessors in conjunction with a DSP core, or any other suchconfiguration).

The functions described herein may be implemented in hardware, softwareexecuted by a processor, firmware, or any combination thereof. Ifimplemented in software executed by a processor, the functions may bestored on or transmitted over as one or more instructions or code on acomputer-readable medium. Other examples and implementations are withinthe scope of the disclosure and appended claims. For example, due to thenature of software, functions described above can be implemented usingsoftware executed by a processor, hardware, firmware, hardwiring, orcombinations of any of these. Features implementing functions may alsobe physically located at various positions, including being distributedsuch that portions of functions are implemented at different physicallocations. Also, as used herein, including in the claims, “or” as usedin a list of items (for example, a list of items prefaced by a phrasesuch as “at least one of” or “one or more of”) indicates an inclusivelist such that, for example, a list of [at least one of A, B, or C]means A or B or C or AB or AC or BC or ABC (i.e., A and B and C).

Further embodiments of the present disclosure include a method ofwireless communication. The method includes transmitting, by a userequipment (UE) in a first cell frequency of a network, a request for anetwork slice of the network that is not provided by the first cellfrequency; and receiving, by the UE in response to the request,information for communicating in a second cell frequency of the networkthat provides the network slice requested.

In some aspects, the method may also include one or more of thefollowing features. For instance, the method includes where thetransmitting includes transmitting, by the UE, a non-access stratum(NAS) registration request message including network slice selectionassistance information (NSSAI), the NSSAI indicating that the networkslice requested is preferred over another network slice of the network.The transmitting includes transmitting, by the UE, a non-access stratum(NAS) service request message indicating the network slice that is notincluded in allowed network slice selection assistance information(NSSAI). The transmitting includes transmitting, by the UE, a protocoldata unit (PDU) session request message indicating the network slicethat is not included in allowed network slice selection assistanceinformation (NSSAI). The transmitting includes transmitting, by the UE,a radio resource control (RRC) message indicating the network slice. Thetransmitting includes transmitting, by the UE, a system informationrequest message requesting frequency information associated with thenetwork slice; and the receiving includes receiving, by the UE, a systeminformation response message including the frequency informationindicating that the network slice is provided by the second cellfrequency. The method may include reselecting, by the UE, to the secondcell frequency based on the frequency information received. Thereceiving includes receiving, by the UE, an instruction to perform atleast one of a handover or a redirection to the second cell frequency.The receiving includes receiving, by the UE, a configuration for atleast one of a dual-connectivity with the second cell frequency or acarrier aggregation with the second cell frequency. The method mayinclude transmitting, by the UE in response to a determination that theconfiguration changes an availability of the network slice, a firstnon-access stratum (NAS) registration request message to obtain a firstupdate of allowed network slice selection assistance information(NSSAI). The method may include receiving, by the UE, a de-configurationfor the at least one the dual-connectivity with the second cellfrequency or the carrier aggregation with the second cell frequency;transmitting, by the UE in response to a determination that thede-configuration changes the availability of the network slice, a secondNAS registration request message to obtain a second update of theallowed NSSAI.

Further embodiments of the present disclosure include a method ofwireless communication. The method includes receiving, by a core networkentity from a base station (BS) operating over a first cell frequency ofa network, a request to provide a network slice of the network to a userequipment (UE), the network slice not provided by the first cellfrequency; and transmitting, by the core network entity to the BS,information associated with a second cell frequency of the networkproviding the network slice.

In some aspects, the method may also include one or more of thefollowing features. For instance, the method includes where thereceiving includes receiving, by the core network entity, a non-accessstratum (NAS) registration request message including network sliceselection assistance information (NSSAI), the NSSAI indicating that theUE prefers the network slice requested over another network slice of thenetwork. The method may include transmitting, by the core network entityto the BS, a message indicating that the UE prefers the network slicerequested over the another network slice. The receiving includesreceiving, by the core network entity, a non-access stratum (NAS)service request message indicating the network slice that is notincluded in allowed network slice selection assistance information(NSSAI). The receiving includes receiving, by the core network entity, aprotocol data unit (PDU) session request message indicating the networkslice that is not included in allowed network slice selection assistanceinformation (NSSAI). The transmitting includes transmitting, by the corenetwork entity to the BS, an instruction to direct the UE to communicatein the second cell frequency.

Further embodiments of the present disclosure include a method ofwireless communication. The method includes obtaining, by a base station(BS), an indication that a user equipment (UE) is interested in anetwork slice of a network not provided by a first cell frequency, theBS in communication with the UE in the first cell frequency; andreceiving, by the BS from a core network entity, information associatedwith a second cell frequency of the network providing the network slice.

In some aspects, the method may also include one or more of thefollowing features. For instance, the method includes where theobtaining includes receiving, by the BS from the core network entity, amessage indicating that the UE prefers the network slice requested overanother network slice of the network. The obtaining includes receiving,by the BS from the UE, a radio resource control (RRC) message includingthe indication. The method may include selecting, by the BS, a targetcell for a handover of the UE based at least in part on the indication.The method may include receiving, by the BS from the UE, a systeminformation request message requesting frequency information associatedwith the network slice; and transmitting, by the BS, a systeminformation response message indicating that the network slice isprovided by the second cell frequency. The method may include receiving,by the BS from the core network entity, an instruction to direct the UEto the second cell frequency. The method may include transmitting, bythe BS to the UE, an instruction to perform a handover to the secondcell frequency based on the information associated with the second cellfrequency. The method may include transmitting, by the BS to the UE, aconfiguration for at least one of a dual-connectivity with the secondcell frequency or a carrier aggregation with the second cell frequency.

Further embodiments of the present disclosure include a user equipment(UE) including a transceiver configured to transmit, in a first cellfrequency of a network, a request for a network slice of the networkthat is not provided by the first cell frequency; and receive, inresponse to the request, an information for communicating in a secondcell frequency of the network that provides the network slice requested.

In some aspects, the UE may also include one or more of the followingfeatures. For instance, the UE includes where the transceiver configuredto transmit the request is further configured to transmit a non-accessstratum (NAS) registration request message including network sliceselection assistance information (NSSAI), the NSSAI indicating that thenetwork slice requested is preferred over another network slice of thenetwork. The method may include transmitting, by the BS to the UE, ade-configuration for the at least one of the dual-connectivity with thesecond cell frequency or a carrier aggregation with the second cellfrequency; transmitting, by the BS to the core network entity inresponse to a determination that the de-configuration changes theavailability of the network slice, an indication of a change of theavailability of the network slice. The transceiver configured totransmit the request is further configured to transmit a non-accessstratum (NAS) service request message indicating the network slice thatis not included in allowed network slice selection assistanceinformation (NSSAI). The transceiver configured to transmit the requestis further configured to transmit a protocol data unit (PDU) sessionrequest message indicating the network slice that is not included inallowed network slice selection assistance information (NSSAI). Thetransceiver configured to transmit the request is further configured totransmit a radio resource control (RRC) message indicating the networkslice. The transceiver configured to transmit the request is furtherconfigured to transmit a system information request message requestingfrequency information associated with the network slice; and thetransceiver configured to receive the information is further configuredto receive system information response message including the frequencyinformation indicating that the network slice is provided by the secondcell frequency. The UE may include a processor configured to reselect tothe second cell frequency based on the frequency information received.The transceiver configured to receive the information is furtherconfigured to receive an instruction to perform a handover to the secondcell frequency. The transceiver configured to receive the information isfurther configured to receive a configuration for at least one of adual-connectivity with the second cell frequency or a carrieraggregation with the second cell frequency. The transceiver is furtherconfigured to transmit, in response to a determination that theconfiguration changes an availability of the network slice, a non-accessstratum (NAS) registration request message to obtain updated allowednetwork slice selection assistance information (NSSAI) in response tothe determination. The transceiver is further configured to receive ade-configuration for the at least one the dual-connectivity with thesecond cell frequency or the carrier aggregation with the second cellfrequency; and transmit, in response to a determination that thede-configuration changes the availability of the network slice, a secondNAS registration request message to obtain a second update of theallowed NSSAI.

Further embodiments of the present disclosure include a core networkentity including a transceiver configured to receive, from a basestation (BS) operating over a first cell frequency of a network, arequest to provide a network slice of the network to a user equipment(UE), the network slice not provided by the first cell frequency; andtransmit, to the BS, information associated with a second cell frequencyof the network providing the network slice.

In some aspects, the core network entity may also include one or more ofthe following features. For instance, the core network entity includeswhere the transceiver configured to receive the request is furtherconfigured to receive a non-access stratum (NAS) registration requestmessage including network slice selection assistance information(NSSAI), the NSSAI indicating that the UE prefers the network slicerequested over another network slice of the network. The transceiver isfurther configured to transmit, to the BS, a message indicating that theUE prefers the network slice requested over the another network slice.The transceiver configured to receive the request is further configuredto receive a non-access stratum (NAS) service request message indicatingthe network slice that is not included in allowed network sliceselection assistance information (NSSAI). The transceiver configured toreceive the request is further configured to receive a protocol dataunit (PDU) session request message indicating the network slice that isnot included in allowed network slice selection assistance information(NSSAI). The transceiver configured to transmit the information isfurther configured to transmit, to the BS, an instruction to direct theUE to communicate in the second cell frequency.

Further embodiments of the present disclosure include a base station(BS) including a processor configured to obtaining an indication that auser equipment (UE) is interested in a network slice of a network notprovided by a first cell frequency, the BS in communication with the UEin the first cell frequency; and a transceiver configured to receiving,by the BS from a core network entity, information associated with asecond cell frequency of the network providing the network slice.

In some aspects, the BS may also include one or more of the followingfeatures. For instance, the BS includes where the processor configuredto obtain the indication is further configured to receive, from the corenetwork entity via the transceiver, a message indicating that the UEprefers the network slice requested over another network slice of thenetwork. The processor configured to obtain the indication is furtherconfigured to receive, from the UE via the transceiver, a radio resourcecontrol (RRC) message including the indication. The processor is furtherconfigured to select a target cell for a handover of the UE based atleast in part on the indication. The transceiver is further configuredto receive, from the UE, a system information request message requestingfrequency information associated with the network slice; and transmit asystem information response message indicating that the network slice isprovided by the second cell frequency. The transceiver is furtherconfigured to receive, from the core network entity, an instruction todirect the UE to the second cell frequency. The transceiver is furtherconfigured to transmit, to the UE, an instruction to perform a handoverto the second cell frequency based on the information associated withthe second cell frequency. The transceiver is further configured totransmit, to the UE, a configuration for at least one of adual-connectivity with the second cell frequency or a carrieraggregation with the second cell frequency. The transceiver is furtherconfigured to transmit, to the core network entity in response to adetermination that the configuration changes an availability of thenetwork slice, an indication of a change of the availability of thenetwork slice requested in response to the determination. Thetransceiver is further configured to transmit, to the UE, ade-configuration for the at least one of the dual-connectivity with thesecond cell frequency or a carrier aggregation with the second cellfrequency; transmit, to the core network entity in response to adetermination that the de-configuration changes the availability of thenetwork slice, an indication of a change of the availability of thenetwork slice.

Further embodiments of the present disclosure include acomputer-readable medium having program code recorded thereon. Thecomputer-readable medium includes code for causing user equipment (UE)to transmit, in a first cell frequency of a network, a request for anetwork slice of the network that is not provided by the first cellfrequency. The computer-readable medium also includes code for causingthe UE to receive, in response to the request, an information forcommunicating in a second cell frequency of the network that providesthe network slice requested.

In some aspects, the computer-readable medium may also include one ormore of the following features. For instance, the computer-readablemedium includes where the code for causing the UE to transmit therequest is further configured to transmit a non-access stratum (NAS)registration request message including network slice selectionassistance information (NSSAI), the NSSAI indicating that the networkslice requested is preferred over another network slice of the network.The code for causing the UE to transmit the request is furtherconfigured to transmit a non-access stratum (NAS) service requestmessage indicating the network slice that is not included in allowednetwork slice selection assistance information (NSSAI). The code forcausing the UE to transmit the request is further configured to transmita protocol data unit (PDU) session request message indicating thenetwork slice that is not included in allowed network slice selectionassistance information (NSSAI). The code for causing the UE to transmitthe request is further configured to transmit a radio resource control(RRC) message indicating the network slice. The code for causing the UEto transmit the request is further configured to transmit a systeminformation request message requesting frequency information associatedwith the network slice; and the code for causing the UE to receive theinformation is further configured to receive system information responsemessage including the frequency information indicating that the networkslice is provided by the second cell frequency. The computer-readablemedium may include code for causing the UE to reselect to the secondcell frequency based on the frequency information received. The code forcausing the UE to receive the information is further configured toreceive an instruction to perform a handover to the second cellfrequency. The code for causing the UE to receive the information isfurther configured to receive a configuration for at least one of adual-connectivity with the second cell frequency or a carrieraggregation with the second cell frequency. The computer-readable mediummay include code for causing the UE to transmit, in response to adetermination that the configuration changes an availability of thenetwork slice, a non-access stratum (NAS) registration request messageto obtain updated allowed network slice selection assistance information(NSSAI) in response to the determination. The computer-readable mediummay include code for causing the UE to receive a de-configuration forthe at least one the dual-connectivity with the second cell frequency orthe carrier aggregation with the second cell frequency; and code forcausing the UE to transmit, in response to a determination that thede-configuration changes the availability of the network slice, a secondnon-access stratum (NAS) registration request message to obtain a secondupdate of the allowed NSSAI.

Further embodiments of the present disclosure include acomputer-readable medium having program code recorded thereon. Thecomputer-readable medium includes code for causing a core network entityto receive, from a base station (BS) operating over a first cellfrequency of a network, a request to provide a network slice of thenetwork to a user equipment (UE), the network slice not provided by thefirst cell frequency. The computer-readable medium also includes codefor causing the core network entity to transmit, to the BS, informationassociated with a second cell frequency of the network providing thenetwork slice.

The computer-readable medium may also include one or more of thefollowing features. In some aspects, the computer-readable mediumincludes where the code for causing the core network entity to receivethe request is further configured to receive a non-access stratum (NAS)registration request message including network slice selectionassistance information (NSSAI), the NSSAI indicating that the UE prefersthe network slice requested over another network slice of the network.The computer-readable medium may include code for causing the corenetwork entity to transmit, to the BS, a message indicating that the UEprefers the network slice requested over the another network slice. Thecode for causing the core network entity to receive the request isfurther configured to receive a non-access stratum (NAS) service requestmessage indicating the network slice that is not included in allowednetwork slice selection assistance information (NSSAI). The code forcausing the core network entity to receive the request is furtherconfigured to receive a protocol data unit (PDU) session request messageindicating the network slice that is not included in allowed networkslice selection assistance information (NSSAI). The code for causing thecore network entity to transmit the information is further configured totransmit, to the BS, an instruction to direct the UE to communicate inthe second cell frequency.

Further embodiments of the present disclosure include acomputer-readable medium having program code recorded thereon. Thecomputer-readable medium includes code for causing a base station (BS)to obtain an indication that a user equipment (UE) is interested in anetwork slice of a network not provided by a first cell frequency, theBS in communication with the UE in the first cell frequency; and codefor causing the BS to receive, from a core network entity, informationassociated with a second cell frequency of the network providing thenetwork slice.

In some aspects, the computer-readable medium may also include one ormore of the following features. For instance, the computer-readablemedium includes where the code for causing the BS to obtain theindication is further configured to receive, from the core networkentity, a message indicating that the UE prefers the network slicerequested over another network slice of the network. The code forcausing the BS to obtain the indication is further configured toreceive, from the UE, a radio resource control (RRC) message includingthe indication. The computer-readable medium may include code forcausing the BS to select a target cell for a handover of the UE based atleast in part on the indication. The computer-readable medium mayinclude code for causing the BS to receive, from the UE, a systeminformation request message requesting frequency information associatedwith the network slice; and code for causing the BS to transmit a systeminformation response message indicating that the network slice isprovided by the second cell frequency. The computer-readable medium mayinclude code for causing the BS to receive, from the core networkentity, an instruction to direct the UE to the second cell frequency.The computer-readable medium may include code for causing the BS totransmit, to the UE, an instruction to perform a handover to the secondcell frequency based on the information associated with the second cellfrequency. The computer-readable medium may include code for causing theBS to transmit, to the UE, a configuration for at least one of adual-connectivity with the second cell frequency or a carrieraggregation with the second cell frequency. The computer-readable mediummay include code for causing the BS to transmit, to the core networkentity in response to a determination that the configuration changes anavailability of the network slice, an indication of a change of theavailability of the network slice requested in response to thedetermination. The computer-readable medium may include code for causingthe BS to transmit, to the UE, a de-configuration for the at least oneof the dual-connectivity with the second cell frequency or a carrieraggregation with the second cell frequency; code for causing the BS totransmit, to the core network entity in response to a determination thatthe de-configuration changes the availability of the network slice, anindication of a change of the availability of the network slice.

Further embodiments of the present disclosure include a user equipment(UE) including means for transmitting, in a first cell frequency of anetwork, a request for a network slice of the network that is notprovided by the first cell frequency. The user equipment also includesmeans for receiving, in response to the request, an information forcommunicating in a second cell frequency of the network that providesthe network slice requested.

In some aspects, the UE may also include one or more of the followingfeatures. For instance, the UE includes where the means for transmittingthe request is further configured to transmit a non-access stratum (NAS)registration request message including network slice selectionassistance information (NSSAI), the NSSAI indicating that the networkslice requested is preferred over another network slice of the network.The means for transmitting the request is further configured to transmita non-access stratum (NAS) service request message indicating thenetwork slice that is not included in allowed network slice selectionassistance information (NSSAI). The means for transmitting the requestis further configured to transmit a protocol data unit (PDU) sessionrequest message indicating the network slice that is not included inallowed network slice selection assistance information (NSSAI). Themeans for transmitting the request is further configured to transmit aradio resource control (RRC) message indicating the network slice. Themeans for transmitting the request is further configured to transmit asystem information request message requesting frequency informationassociated with the network slice; and the means for receiving theinformation is further configured to receive system information responsemessage including the frequency information indicating that the networkslice is provided by the second cell frequency. The UE may include meansfor reselecting to the second cell frequency based on the frequencyinformation received. The means for receiving the information is furtherconfigured to receiving an instruction to perform a handover to thesecond cell frequency. The means for receiving the information isfurther configured to receiving a configuration for at least one of adual-connectivity with the second cell frequency or a carrieraggregation with the second cell frequency. The UE may include means fortransmitting a non-access stratum (NAS) registration request message toobtain updated allowed network slice selection assistance information(NSSAI) in response to a determination that the configuration changes anavailability of the network slice. The UE may include means forreceiving a de-configuration for the at least one the dual-connectivitywith the second cell frequency or the carrier aggregation with thesecond cell frequency; and means for transmitting, in response to adetermination that the de-configuration changes the availability of thenetwork slice, a second non-access stratum (NAS) registration requestmessage to obtain a second update of the allowed NSSAI.

Further embodiments of the present disclosure include a core networkentity including means for receiving, from a base station (BS) operatingover a first cell frequency of a network, a request to provide a networkslice of the network to a user equipment (UE), the network slice notprovided by the first cell frequency. The core network entity alsoincludes means for transmitting, to the BS, information associated witha second cell frequency of the network providing the network slice.

In some aspects, the core network entity may also include one or more ofthe following features. For instance, the core network entity includeswhere the means for receiving the request is further configured toreceive a non-access stratum (NAS) registration request messageincluding network slice selection assistance information (NSSAI), theNSSAI indicating that the UE prefers the network slice requested overanother network slice of the network. The core network entity mayinclude means for transmitting, to the BS, a message indicating that theUE prefers the network slice requested over the another network slice.The means for receiving the request is further configured to receiving anon-access stratum (NAS) service request message indicating the networkslice that is not included in allowed network slice selection assistanceinformation (NSSAI). The means for receiving the request is furtherconfigured to receiving a protocol data unit (PDU) session requestmessage indicating the network slice that is not included in allowednetwork slice selection assistance information (NSSAI). The means fortransmitting the information is further configured to transmitting, tothe BS, an instruction to direct the UE to communicate in the secondcell frequency.

Further embodiments of the present disclosure include a base station(BS) including means for obtaining an indication that a user equipment(UE) is interested in a network slice of a network not provided by afirst cell frequency, the BS in communication with the UE in the firstcell frequency; and means for receiving, from a core network entity,information associated with a second cell frequency of the networkproviding the network slice.

In some aspects, the BS may also include one or more of the followingfeatures. For instance, the BS includes where the means for obtainingthe indication is further configured to receive, from the core networkentity, a message indicating that the UE prefers the network slicerequested over another network slice of the network. The means forobtaining the indication is further configured to receive, from the UE,a radio resource control (RRC) message including the indication. The BSmay include means for selecting a target cell for a handover of the UEbased at least in part on the indication. The BS may include means forreceiving, from the UE, a system information request message requestingfrequency information associated with the network slice; and means fortransmitting a system information response message indicating that thenetwork slice is provided by the second cell frequency. The BS mayinclude means for receiving, from the core network entity, aninstruction to direct the UE to the second cell frequency. The BS mayinclude means for transmitting, to the UE, an instruction to perform ahandover to the second cell frequency based on the informationassociated with the second cell frequency. The BS may include means fortransmitting, to the UE, a configuration for at least one of adual-connectivity with the second cell frequency or a carrieraggregation with the second cell frequency. The BS may include means fortransmitting, to the core network in response to a determination thatthe configuration changes an availability of the network slice, anindication of a change of the availability of the network slicerequested. The BS may include means for transmitting, to the UE, ade-configuration for the at least one of the dual-connectivity with thesecond cell frequency or a carrier aggregation with the second cellfrequency; means for transmitting, to the core network entity inresponse to a determination that the de-configuration changes theavailability of the network slice, an indication of a change of theavailability of the network slice.

As those of some skill in this art will by now appreciate and dependingon the particular application at hand, many modifications, substitutionsand variations can be made in and to the materials, apparatus,configurations and methods of use of the devices of the presentdisclosure without departing from the spirit and scope thereof. In lightof this, the scope of the present disclosure should not be limited tothat of the particular embodiments illustrated and described herein, asthey are merely by way of some examples thereof, but rather, should befully commensurate with that of the claims appended hereafter and theirfunctional equivalents.

What is claimed is:
 1. A method of wireless communication performed by anetwork entity, comprising: obtaining an indication that a userequipment (UE) is interested in a network slice of a network notprovided by a first cell frequency, the network entity in communicationwith the UE in the first cell frequency; and receiving, from a corenetwork entity, information associated with a second cell frequency ofthe network providing the network slice.
 2. The method of claim 1,wherein the obtaining includes: receiving, from the core network entity,a message indicating that the UE prefers the network slice requestedover another network slice of the network.
 3. The method of claim 1,wherein the obtaining includes: receiving, from the UE, a radio resourcecontrol (RRC) message including the indication.
 4. The method of claim3, further comprising: selecting a target cell for a handover of the UEbased at least in part on the indication.
 5. The method of claim 1,further comprising: receiving, from the UE, a system information requestmessage requesting frequency information associated with the networkslice; and transmitting a system information response message indicatingthat the network slice is provided by the second cell frequency.
 6. Themethod of claim 1, further comprising: receiving, from the core networkentity, an instruction to direct the UE to the second cell frequency. 7.The method of claim 1, further comprising: transmitting, to the UE, aninstruction to perform a handover to the second cell frequency based onthe information associated with the second cell frequency.
 8. The methodof claim 1, further comprising: transmitting, to the UE, a configurationfor at least one of a dual-connectivity with the second cell frequencyor a carrier aggregation with the second cell frequency.
 9. A networkentity, comprising: a memory; a transceiver; and a processor incommunication with the memory and the transceiver, wherein the networkentity is configured to: obtain an indication that a user equipment (UE)is interested in a network slice of a network not provided by a firstcell frequency, the network entity in communication with the UE in thefirst cell frequency; and receive, from a core network entity,information associated with a second cell frequency of the networkproviding the network slice.
 10. The network entity of claim 9, whereinthe network entity is configured to: receive, from the core networkentity via the transceiver, a first message indicating that the UEprefers the network slice requested over another network slice of thenetwork; obtain the indication that the UE is interested in the networkslice of the network not provided by the first cell frequency from thereceived message.
 11. The network entity of claim 9, wherein the networkentity is configured to: receive, from the UE via the transceiver, aradio resource control (RRC) message including the indication that theUE is interested in the network slice of the network not provided by thefirst cell frequency; and transmit, to the UE, an instruction to performa handover to the second cell frequency based on at least one of theinformation associated with the second cell frequency and indicationthat the UE is interested in the network slice of the network notprovided by the first cell frequency.
 12. The network entity of claim 9,wherein the network entity is further configured to: receive, from theUE, a system information request message requesting frequencyinformation associated with the network slice; and transmit a systeminformation response message indicating that the network slice isprovided by the second cell frequency.
 13. The network entity of claim9, wherein the network entity is further configured to: receive, fromthe core network entity, an instruction to direct the UE to the secondcell frequency; transmit, to the UE, at least one of: an instruction toperform a handover to the second cell frequency based on the informationassociated with the second cell frequency; or a configuration for atleast one of a dual-connectivity with the second cell frequency or acarrier aggregation with the second cell frequency.
 14. Anon-transitory, computer-readable medium having program code recordedthereon, wherein the program code comprises instructions executable by aprocessor of a network entity to cause the network entity to: obtain anindication that a user equipment (UE) is interested in a network sliceof a network not provided by a first cell frequency, the network entityin communication with the UE in the first cell frequency; and receive,from a core network entity, information associated with a second cellfrequency of the network providing the network slice.
 15. Thenon-transitory, computer-readable medium of claim 14, wherein theinstructions causing the network entity to obtain the indicationcomprises instructions causing the network entity to: receive, from thecore network entity, a message indicating that the UE prefers thenetwork slice requested over another network slice of the network. 16.The non-transitory, computer-readable medium of claim 14, wherein theinstructions causing the network entity to obtain the indicationcomprises instructions causing the network entity to: receive, from theUE, a radio resource control (RRC) message including the indication. 17.The non-transitory, computer-readable medium of claim 16, wherein theprogram code further comprises instructions causing the network entityto: select a target cell for a handover of the UE based at least in parton the indication.
 18. The non-transitory, computer-readable medium ofclaim 14, wherein the program code further comprises instructionscausing the network entity to: receive, from the UE, a systeminformation request message requesting frequency information associatedwith the network slice; and transmit a system information responsemessage indicating that the network slice is provided by the second cellfrequency.
 19. The non-transitory, computer-readable medium of claim 14,wherein the program code further comprises instructions causing thenetwork entity to: receive, from the core network entity, an instructionto direct the UE to the second cell frequency.
 20. The non-transitory,computer-readable medium of claim 14, wherein the program code furthercomprises instructions causing the network entity to: transmit, to theUE, an instruction to perform a handover to the second cell frequencybased on the information associated with the second cell frequency. 21.The non-transitory, computer-readable medium of claim 14, wherein theprogram code further comprises instructions causing the network entityto: transmit, to the UE, a configuration for at least one of adual-connectivity with the second cell frequency or a carrieraggregation with the second cell frequency.
 22. A network entity,comprising: means for obtaining an indication that a user equipment (UE)is interested in a network slice of a network not provided by a firstcell frequency, the network entity in communication with the UE in thefirst cell frequency; and means for receiving, from a core networkentity, information associated with a second cell frequency of thenetwork providing the network slice.
 23. The network entity of claim 22,wherein the means for obtaining includes: means for receiving, from thecore network entity, a message indicating that the UE prefers thenetwork slice requested over another network slice of the network. 24.The network entity of claim 22, wherein the means for obtainingincludes: means for receiving, from the UE, a radio resource control(RRC) message including the indication.
 25. The network entity of claim24, further comprising: means for selecting a target cell for a handoverof the UE based at least in part on the indication.
 26. The networkentity of claim 22, further comprising: means for receiving, from theUE, a system information request message requesting frequencyinformation associated with the network slice; and means fortransmitting a system information response message indicating that thenetwork slice is provided by the second cell frequency.
 27. The networkentity of claim 22, further comprising: means for receiving, from thecore network entity, an instruction to direct the UE to the second cellfrequency.
 28. The network entity of claim 22, further comprising: meansfor transmitting, to the UE, an instruction to perform a handover to thesecond cell frequency based on the information associated with thesecond cell frequency.
 29. The network entity of claim 22, furthercomprising: means for transmitting, to the UE, a configuration for atleast one of a dual-connectivity with the second cell frequency or acarrier aggregation with the second cell frequency.